Agent skill

Test Hardening

by WellApp-ai in WellApp-ai/Well

Convert passed QA Contract criteria to automated tests. An agent skill from WellApp-ai/Well.

MITAuto-check passedTesting & QA

Install Test Hardening

skills CLI
$ npx skills add WellApp-ai/Well --skill test-hardening -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install WellApp-ai/Well test-hardening --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/WellApp-ai/Well.git skills-src && mkdir -p .claude/skills && cp -r skills-src/cursor-rules/skills/test-hardening .claude/skills/test-hardening && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
test-hardening
GitHub stars
345
Token cost
~1.3k tokens
SKILL.md length
294 words
Files
1
Skills in repo
36
Repo updated
First seen
Licence
MIT

At a glance

Convert passed QA Contract criteria to automated tests. An agent skill from WellApp-ai/Well.

  • Works in 6 steps: Analyze Criteria → Generate Backend Tests (G#N) → Generate Storybook Stories (AC#N - States) → …
  • Tasks that involve Test generation
  • SKILL.md covers When to Use, Input: Verification Report, Phase 1: Analyze Criteria and Phase 2: Generate Backend…, plus 6 more sections
  • Calls npm and npx

What it does

Test Hardening is an agent skill from WellApp-ai/Well. Convert passed QA Contract criteria to automated tests

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering Test generation. It works with Storybook. The repository describes itself as: No more Sundays on Finance. We build the infrastructure that retrieves, processes, and routes your financial and business data to your FinOps stack, so founders can ship, not… The licence is MIT.

When your agent uses it

  • Tasks that involve Test generation

Example prompts

  • “/test-hardening”

Requirements

  • Node.js

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Analyze Criteria
  2. Generate Backend Tests (G#N)
  3. Generate Storybook Stories (AC#N - States)
  4. Generate E2E Tests (AC#N - Interactions)
  5. Verify Tests Pass
  6. Update Test Summary

What it can do on your machine

Read from SKILL.md and the folder at commit c740217. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npm
    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npm and npx, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Test Hardening loads about 1.3k tokens when it runs. Until then it costs about 17 tokens; SKILL.md has 294 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~17
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from WellApp-ai/Well at commit c740217, republished under its MIT licence (© WellApp-ai). 294 words, ~1,340 tokens.

Download SKILL.mdSave it as .claude/skills/test-hardening/SKILL.md (or your agent's skills folder).
name
test-hardening
description
Convert passed QA Contract criteria to automated tests

Test Hardening Skill

Convert verified QA Contract criteria (G#N, AC#N) into permanent automated tests. Ensures passing scenarios become regression tests.

When to Use

  • After qa-commit returns GREEN for a commit
  • After debug skill fixes an issue (Phase 7: Harden)
  • Before pushing PR (ensure all criteria have tests)
  • Manually with "use test-hardening skill"

Input: Verification Report

From qa-commit's Verification Report:

  • List of passed G#N (Gherkin scenarios)
  • List of passed AC#N (acceptance criteria)

Phase 1: Analyze Criteria

1.1 Categorize by Test Type
Criteria TypeTest FrameworkLocation
G#N (Backend)Jestapps/api/**/*.test.ts
AC#N (UI State)Storybook**/*.stories.tsx
AC#N (Interaction)Playwrighttests/e2e/**/*.spec.ts
1.2 Check Existing Tests
Grep: "G#[N]" or "[scenario name]" in test files

Skip if test already exists.

Phase 2: Generate Backend Tests (G#N)

For each passed G#N without existing test:

2.1 Template
typescript
// apps/api/src/[feature]/__tests__/[feature].test.ts

describe('[Feature Name]', () => {
  // G#1: [Scenario name]
  it('should [expected behavior]', async () => {
    // Arrange
    const input = { /* test data */ };
    
    // Act
    const response = await request(app)
      .[method]('[endpoint]')
      .send(input);
    
    // Assert
    expect(response.status).toBe([status]);
    expect(response.body).toMatchObject({ /* expected */ });
  });

  // G#2: [Scenario name]
  it('should return [error] when [condition]', async () => {
    // Test implementation
  });
});
2.2 Generate Test
  1. Extract endpoint, method, expected response from G#N
  2. Create test file if not exists
  3. Add test case with G#N reference in comment
  4. Run test to verify it passes
bash
npm run test -- --grep "[scenario name]"

Phase 3: Generate Storybook Stories (AC#N - States)

For state-based AC#N:

3.1 Template
typescript
// apps/web/src/[component]/[Component].stories.tsx

import type { Meta, StoryObj } from '@storybook/react';
import { Component } from './Component';

const meta: Meta<typeof Component> = {
  title: 'Features/[Feature]/[Component]',
  component: Component,
};

export default meta;
type Story = StoryObj<typeof Component>;

// AC#1: Renders without error
export const Default: Story = {
  args: { /* default props */ },
};

// AC#2: Shows loading state
export const Loading: Story = {
  args: { isLoading: true },
};

// AC#3: Shows error state
export const Error: Story = {
  args: { error: 'Something went wrong' },
};

// AC#4: Shows empty state
export const Empty: Story = {
  args: { data: [] },
};
3.2 Generate Story
  1. Check if stories file exists
  2. Add missing story variants for each AC#N
  3. Run Storybook to verify renders
bash
npm run storybook -- --smoke-test

Phase 4: Generate E2E Tests (AC#N - Interactions)

For interaction-based AC#N:

4.1 Template
typescript
// tests/e2e/[feature].spec.ts

import { test, expect } from '@playwright/test';

test.describe('[Feature Name]', () => {
  // AC#5: User can submit form
  test('should allow form submission', async ({ page }) => {
    await page.goto('/[route]');
    
    await page.fill('[name="field"]', 'value');
    await page.click('[type="submit"]');
    
    await expect(page.locator('.success')).toBeVisible();
  });

  // AC#6: Keyboard navigation works
  test('should support keyboard navigation', async ({ page }) => {
    await page.goto('/[route]');
    
    await page.keyboard.press('Tab');
    await expect(page.locator(':focus')).toHaveAttribute('name', 'first-field');
  });
});
4.2 Generate Test
  1. Check if E2E test file exists
  2. Add test case for each interaction AC#N
  3. Run Playwright to verify
bash
npx playwright test [feature].spec.ts

Phase 5: Verify Tests Pass

Run all generated tests:

bash
# Backend
npm run test

# Storybook
npm run storybook -- --smoke-test

# E2E (if applicable)
npx playwright test

Phase 6: Update Test Summary

markdown
## Test Hardening Report

### Generated Tests

| Criteria | Type | File | Status |
|----------|------|------|--------|
| G#1 | Jest | `[path]` | CREATED/EXISTS |
| G#2 | Jest | `[path]` | CREATED/EXISTS |
| AC#1 | Storybook | `[path]` | CREATED/EXISTS |
| AC#3 | Playwright | `[path]` | CREATED/EXISTS |

### Test Results

| Suite | Total | Passed | Failed |
|-------|-------|--------|--------|
| Jest | [N] | [N] | 0 |
| Storybook | [N] | [N] | 0 |
| Playwright | [N] | [N] | 0 |

### Coverage Update

- Backend: [N]% → [N]%
- Frontend: [N]% → [N]%

Integration with Debug

When invoked from debug skill Phase 7 (Harden):

  1. Receive the reproduction steps from debug
  2. Create regression test to prevent recurrence
  3. Add test with reference to original issue
typescript
// Regression test for [issue description]
// Debug session: [date]
it('should not [bug behavior] when [condition]', async () => {
  // Reproduction steps from debug
});

Invocation

Invoked by:

  • qa-commit - After GREEN verdict
  • debug - Phase 7 Harden
  • Push-pr mode - Pre-push verification

Or manually with "use test-hardening skill".

© WellApp-ai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in cursor-rules/skills/test-hardening of WellApp-ai/Well.

Open the folder on GitHubat commit c740217

Compare with similar skills

Test Hardening next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Test Hardening compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Test Hardening this skillWellApp-ai/Well345—~1.3kAutomated safety check: PassMIT
Write and Verify Playwright Testsappsmithorg/appsmith41k—~2.9kAutomated safety check: NotesApache-2.0
Adk Verify Snippetsgoogle/adk-python22k—~1.4kAutomated safety check: PassApache-2.0
Engine E2Ewix/react-native-navigation13k—~1.1kAutomated safety check: PassMIT
Hermetic Python Unit TestsdimensionalOS/dimos4.6k—~1.4kAutomated safety check: PassCustom licence
Emcaklofas/kicad-happy1.4k1 repos~2.8kAutomated safety check: PassMIT

Similar skills

  • Writes a Playwright end-to-end test from a prompt, runs it against a live Appsmith deployment and retries with fixes up to three times until it passes.

    41k GitHub stars~2.9k tokensUpdated yesterday
    Testing & QAAuto-check: notes
  • Adk Verify Snippets

    google/adk-python

    Official

    Checks that every Python code block in a Markdown file actually compiles and runs, by extracting each block to a temporary file, executing it in an isolated subprocess, and writing a pass/fail…

    22k GitHub stars~1.4k tokensUpdated today
    Testing & QAAuto-check passed
  • Engine E2E

    wix/react-native-navigation

    Official

    Run Wix Engine (mobile-apps-engine) iOS E2E tests locally to validate RNN changes.

    13k GitHub stars~1.1k tokensUpdated 5 days ago
    Testing & QAAuto-check passed
  • Hermetic Python Unit Tests

    dimensionalOS/dimos

    Rules for writing, fixing and reviewing pytest unit tests that are hermetic: behavior-focused, deterministic, isolated and cheap to run.

    4.6k GitHub stars~1.4k tokensUpdated today
    Testing & QAAuto-check passed
  • Emc

    aklofas/kicad-happy

    EMC pre-compliance risk analysis for KiCad PCB designs — 18 check categories, 44 rule IDs covering ground planes, decoupling, I/O filtering, switching harmonics, clock routing, differential pair…

    1.4k GitHub starsUsed in 1 repo~2.8k tokens
    Testing & QAAuto-check passed
  • Swig Test

    swig/swig

    Run SWIG test suite for specific languages. An agent skill from swig/swig.

    6.3k GitHub stars~2.3k tokensUpdated 4 days ago
    Testing & QAAuto-check passed

More from WellApp-ai/Well

All 36 skills in this repo
  • Tech Divergence

    WellApp-ai/Well

    Evaluate technical options with scoring matrix, trigger Gate 4 for significant decisions

    345 GitHub stars~1.3k tokensUpdated 3 days ago
    Auto-check passed
  • Ar Aging

    WellApp-ai/Well

    Produce an accounts-receivable aging report and surface overdue invoices for a Well workspace.

    345 GitHub stars~532 tokensUpdated 3 days ago
    Auto-check passed
  • Autonomous Loop

    WellApp-ai/Well

    Iterate until success or limit, composing existing skills with Jidoka integration

    345 GitHub stars~1k tokensUpdated 3 days ago
    Auto-check passed
  • Balance Sheet

    WellApp-ai/Well

    Build a balance sheet (bilan) from a Well workspace. An agent skill from WellApp-ai/Well.

    345 GitHub stars~534 tokensUpdated 3 days ago
    Auto-check passed
  • Bpmn Workflow

    WellApp-ai/Well

    Generate and maintain BPMN 2.0 diagrams linked to Gherkin scenarios

    345 GitHub stars~1.4k tokensUpdated 3 days ago
    Auto-check passed
  • Cash Flow Forecast

    WellApp-ai/Well

    Forecast cash flow and runway for a Well workspace from booked invoices and collected bank transactions.

    345 GitHub stars~567 tokensUpdated 3 days ago
    Auto-check passed

Works with

Categories

Questions about Test Hardening

What does Test Hardening do?

Convert passed QA Contract criteria to automated tests. An agent skill from WellApp-ai/Well. Test Hardening is an agent skill from WellApp-ai/Well.

When should I use Test Hardening?

Test Hardening fits situations like: tasks that involve Test generation.

How do I install Test Hardening in Claude Code?

Run `npx skills add WellApp-ai/Well --skill test-hardening -a claude-code`. Or copy the skill folder (cursor-rules/skills/test-hardening in WellApp-ai/Well) into .claude/skills/test-hardening in your project. Claude Code loads it when a task matches its description.

How do I install Test Hardening in Codex?

Run `npx skills add WellApp-ai/Well --skill test-hardening -a codex`. Or copy the skill folder (cursor-rules/skills/test-hardening in WellApp-ai/Well) into .agents/skills/test-hardening in your project. Codex loads it when a task matches its description.

Can I use Test Hardening in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add WellApp-ai/Well --skill test-hardening -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/test-hardening, .gemini/skills/test-hardening, .github/skills/test-hardening and .opencode/skills/test-hardening in your project.

What does Test Hardening need to run?

Going by SKILL.md and its folder, Test Hardening needs the command-line tools its instructions call (npm and npx). Our summary lists: Node.js.

Does Test Hardening access the network?

SKILL.md contains no URLs. Its commands use npm and npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Test Hardening safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Test Hardening use?

Test Hardening is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Test Hardening use?

About 1.3k tokens (SKILL.md is roughly 5.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Test Hardening?

Skills that share tags, products or a category with Test Hardening: Write and Verify Playwright Tests (appsmithorg/appsmith, 41k stars), Adk Verify Snippets (google/adk-python, 22k stars), Engine E2E (wix/react-native-navigation, 13k stars) and Hermetic Python Unit Tests (dimensionalOS/dimos, 4.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Test Hardening?

WellApp-ai (a GitHub organization) maintains it in WellApp-ai/Well, which has 345 GitHub stars. The repository holds 36 skills in this directory. The repository was last updated on October 7, 2026.

Source: WellApp-ai/Well on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.