Agent skill

QA Commit

Verify implementation against QA Contract (GN, ACN), auto-invoke debug on RED

MITAuto-check passedDevelopment

Install QA Commit

skills CLI

$ npx skills add WellApp-ai/Well --skill qa-commit -a claude-code

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

GitHub CLI

$ gh skill install WellApp-ai/Well qa-commit --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/qa-commit .claude/skills/qa-commit && 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/

Paste into Claude Code

Install the "qa-commit" agent skill from https://github.com/WellApp-ai/Well/tree/main/cursor-rules/skills/qa-commit into .claude/skills/qa-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qa-commit", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/WellApp-ai/Well/tree/main/cursor-rules/skills/qa-commit

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add WellApp-ai/Well --skill qa-commit -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install WellApp-ai/Well qa-commit --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/WellApp-ai/Well.git skills-src && mkdir -p .agents/skills && cp -r skills-src/cursor-rules/skills/qa-commit .agents/skills/qa-commit && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "qa-commit" agent skill from https://github.com/WellApp-ai/Well/tree/main/cursor-rules/skills/qa-commit into .agents/skills/qa-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qa-commit", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add WellApp-ai/Well --skill qa-commit -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install WellApp-ai/Well qa-commit --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/WellApp-ai/Well.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/cursor-rules/skills/qa-commit .cursor/skills/qa-commit && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "qa-commit" agent skill from https://github.com/WellApp-ai/Well/tree/main/cursor-rules/skills/qa-commit into .cursor/skills/qa-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qa-commit", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/WellApp-ai/Well.git --path cursor-rules/skills/qa-commit

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add WellApp-ai/Well --skill qa-commit -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install WellApp-ai/Well qa-commit --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/WellApp-ai/Well.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/cursor-rules/skills/qa-commit .gemini/skills/qa-commit && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "qa-commit" agent skill from https://github.com/WellApp-ai/Well/tree/main/cursor-rules/skills/qa-commit into .gemini/skills/qa-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qa-commit", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install WellApp-ai/Well qa-commit

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add WellApp-ai/Well --skill qa-commit -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/WellApp-ai/Well.git skills-src && mkdir -p .github/skills && cp -r skills-src/cursor-rules/skills/qa-commit .github/skills/qa-commit && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "qa-commit" agent skill from https://github.com/WellApp-ai/Well/tree/main/cursor-rules/skills/qa-commit into .github/skills/qa-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qa-commit", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add WellApp-ai/Well --skill qa-commit -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install WellApp-ai/Well qa-commit --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/WellApp-ai/Well.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/cursor-rules/skills/qa-commit .opencode/skills/qa-commit && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "qa-commit" agent skill from https://github.com/WellApp-ai/Well/tree/main/cursor-rules/skills/qa-commit into .opencode/skills/qa-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qa-commit", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: qa-commit
GitHub stars: 345
Token cost: ~1.2k tokens
SKILL.md length: 334 words
Files: 1
Skills in repo: 36
Repo updated: Sep 30, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Verify implementation against QA Contract (GN, ACN), auto-invoke debug on RED

Works in 6 steps: Load QA Contract → Technical Validation → Gherkin Verification (Backend - G#N) → …
Development work in your project
SKILL.md covers When to Use, Input: Commit Context, Phase 1: Load QA Contract and Phase 2: Technical Validation, plus 7 more sections
Calls npm

What it does

QA Commit is an agent skill from WellApp-ai/Well. Verify implementation against QA Contract (GN, ACN), auto-invoke debug on RED

Its SKILL.md is about 1.2k 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 Development. 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

Development work in your project

Example prompts

“/qa-commit”

Workflow steps

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

Load QA Contract
Technical Validation
Gherkin Verification (Backend - G#N)
Acceptance Verification (Frontend - AC#N)
Generate Verification Report
Handle Verdict

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
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm, 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

QA Commit loads about 1.2k tokens when it runs. Until then it costs about 22 tokens; SKILL.md has 334 words of instructions outside code blocks.

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

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). 334 words, ~1,201 tokens.

Download SKILL.mdSave it as .claude/skills/qa-commit/SKILL.md (or your agent's skills folder).

name: qa-commit
description: Verify implementation against QA Contract (G#N, AC#N), auto-invoke debug on RED

QA Commit Skill

Verify that the current commit satisfies its assigned QA Contract criteria (G#N Gherkin scenarios and AC#N acceptance criteria). Returns GREEN (pass) or RED (fail, triggers debug).

When to Use

After pr-review passes, before git commit
During Agent Mode commit-level workflow
Manually with "use qa-commit skill"

Input: Commit Context

Before running, identify:

Current commit from Commit Plan
Assigned criteria: "Satisfies: G#X, AC#Y, ..."
Related files being changed

Phase 1: Load QA Contract

Retrieve the assigned criteria for this commit:

markdown

## Commit: [Name]
**Satisfies:** G#1, G#2, AC#1, AC#3

### Criteria to Verify:
- G#1: [Scenario description]
- G#2: [Scenario description]
- AC#1: [Acceptance criteria]
- AC#3: [Acceptance criteria]

Phase 2: Technical Validation

Use Cursor tools for technical checks:

2.1 ReadLints

ReadLints:
  paths: [changed files]

Expect: No errors related to committed functionality

2.2 Type Safety

bash

npm run typecheck

Expect: Exit code 0

bash

npm run test -- --grep "[feature name]"

Expect: All tests pass

Phase 3: Gherkin Verification (Backend - G#N)

For each G#N assigned to this commit:

3.1 Endpoint Existence

Verify the API endpoint exists and is implemented:

SemanticSearch: "Where is [endpoint] implemented?"

3.2 Response Shape

Check response matches expected schema:

Grep: "interface.*Response" in related files

3.3 Error Handling

Verify error cases are handled:

Grep: "throw|catch|error" in handler files

Gherkin Checklist

G#N	Scenario	Status	Notes
G#1	[Name]	PASS/FAIL	[Details]
G#2	[Name]	PASS/FAIL	[Details]

Phase 4: Acceptance Verification (Frontend - AC#N)

For each AC#N assigned to this commit:

4.1 Component Existence

Verify component is implemented:

Glob: **/*[ComponentName]*.tsx

4.2 Storybook Story (if AC involves visual)

Check Storybook story exists:

Glob: **/*[ComponentName]*.stories.tsx

4.3 Browser MCP Verification (if running)

For interactive acceptance criteria:

Browser MCP:
1. browser_navigate to Storybook URL
2. browser_snapshot to check state
3. browser_click/browser_type to test interaction
4. browser_take_screenshot for evidence

Acceptance Checklist

AC#N	Criteria	Status	Evidence
AC#1	[Criteria]	PASS/FAIL	[Screenshot/Notes]
AC#3	[Criteria]	PASS/FAIL	[Screenshot/Notes]

Phase 5: Generate Verification Report

markdown

## Verification Report

**Commit:** [Name]
**Satisfies:** G#1, G#2, AC#1, AC#3

### Technical Validation

| Check | Status |
|-------|--------|
| ReadLints | PASS/FAIL |
| TypeCheck | PASS/FAIL |
| Tests | PASS/FAIL/SKIP |

### Gherkin Scenarios (Backend)

| ID | Scenario | Status | Notes |
|----|----------|--------|-------|
| G#1 | [Name] | PASS/FAIL | [Details] |
| G#2 | [Name] | PASS/FAIL | [Details] |

### Acceptance Criteria (Frontend)

| ID | Criteria | Status | Evidence |
|----|----------|--------|----------|
| AC#1 | [Criteria] | PASS/FAIL | [Link/Notes] |
| AC#3 | [Criteria] | PASS/FAIL | [Link/Notes] |

### Verdict

**[GREEN / RED]**

[If GREEN: All criteria verified, ready to commit]
[If RED: Failed criteria listed, invoking debug skill]

Phase 6: Handle Verdict

GREEN Verdict

markdown

All criteria verified. Proceeding to git commit.

RED Verdict - Auto-Invoke Debug

markdown

**Verification failed. Auto-invoking debug skill.**

### Failed Criteria:
- [G#N or AC#N]: [What failed]
- [G#N or AC#N]: [What failed]

### Context for Debug:
- Error messages: [from ReadLints]
- Expected behavior: [from QA Contract]
- Actual behavior: [observed]

Invoking debug skill with context...

After debug fixes, re-run qa-commit to verify.

Integration with Debug

When verdict is RED:

Automatically invoke debug skill
Pass context:
- Failed G#N or AC#N
- Error messages from ReadLints/Shell
- Browser console/network errors (if applicable)
Debug skill fixes issue
Re-run qa-commit
Repeat until GREEN or user intervention

MCP Tools Used

Tool	Purpose
ReadLints	Get lint/type errors
Shell	Run tests, typecheck
Browser MCP	Storybook verification
SemanticSearch	Find implementations
Grep	Search for patterns

Invocation

Invoked by:

commit.mdc - After pr-review passes
agent.mdc - Part of commit-level workflow

Or manually with "use qa-commit skill".

Files

Just SKILL.md in cursor-rules/skills/qa-commit of WellApp-ai/Well.

Open the folder on GitHubat commit c740217

Compare with similar skills

QA Commit 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.

QA Commit compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
QA Commit this skillWellApp-ai/Well	345	—	~1.2k	Automated safety check: Pass	MIT	7 days ago
Review PRrazorpay/blade	656	—	~1.1k	Automated safety check: Pass	MIT	today
Clean Vmaxeldelafosse/loop	281	—	~906	Automated safety check: Pass	MIT	6 mo ago
Qovery Console StandardsQovery/console	227	—	~924	Automated safety check: Pass	MIT	yesterday
Dx Insight Usage Guardrailcultureamp/kaizen-design-system	176	—	~1.3k	Automated safety check: Pass	MIT	yesterday
Tsconfigsredis/RedisInsight	8.9k	—	~1.3k	Automated safety check: Pass	Custom licence	3 days ago

Similar skills

Review PR
razorpay/blade
Review blade PRs by fetching diff, checking CI status, and getting Storybook URL.
656 GitHub stars~1.1k tokensUpdated today
DevelopmentAuto-check passed
Clean Vm
axeldelafosse/loop
Safely clean the local loop VM by reporting and removing stale loop runs, inactive Next.js or Storybook servers, optional browser windows, and unused loop-created worktrees without disturbing active…
281 GitHub stars~906 tokensUpdated 6 mo ago
DevelopmentAuto-check passed
Qovery Console Standards
Qovery/console
Qovery Console coding standards, architecture guidelines, naming conventions, testing practices, and development workflows.
227 GitHub stars~924 tokensUpdated yesterday
DevelopmentAuto-check passed
Dx Insight Usage Guardrail
cultureamp/kaizen-design-system
Checks deps update in widely consumed repos will cause problems or not, and ranks dependency updates by downstream impact for prioritisation.
176 GitHub stars~1.3k tokensUpdated yesterday
Frontend & DesignAuto-check passed
Tsconfigs
redis/RedisInsight
Official
Locate and modify TypeScript configuration in RedisInsight. An agent skill from redis/RedisInsight.
8.9k GitHub stars~1.3k tokensUpdated 3 days ago
DevelopmentAuto-check passed
Handoff
closedloop-ai/claude-plugins
Finish a vibe session in symphony-alpha and hand it to design, then engineering.
122 GitHub stars~2.9k tokensUpdated today
DevelopmentAuto-check passed

Questions about QA Commit

What does QA Commit do?

Verify implementation against QA Contract (GN, ACN), auto-invoke debug on RED. QA Commit is an agent skill from WellApp-ai/Well.

When should I use QA Commit?

QA Commit fits situations like: development work in your project.

How do I install QA Commit in Claude Code?

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

How do I install QA Commit in Codex?

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

Can I use QA Commit 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 qa-commit -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/qa-commit, .gemini/skills/qa-commit, .github/skills/qa-commit and .opencode/skills/qa-commit in your project.

What does QA Commit need to run?

Going by SKILL.md and its folder, QA Commit needs the command-line tools its instructions call (npm).

Does QA Commit access the network?

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

Is QA Commit 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 QA Commit use?

QA Commit 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 QA Commit use?

About 1.2k tokens (SKILL.md is roughly 4.8k 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 QA Commit?

Skills that share tags, products or a category with QA Commit: Review PR (razorpay/blade, 656 stars), Clean Vm (axeldelafosse/loop, 281 stars), Qovery Console Standards (Qovery/console, 227 stars) and Dx Insight Usage Guardrail (cultureamp/kaizen-design-system, 176 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains QA Commit?

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 September 30, 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.

Install QA Commit

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

QA Commit Skill

When to Use

Input: Commit Context

Phase 1: Load QA Contract

Phase 2: Technical Validation

2.1 ReadLints

2.2 Type Safety

2.3 Related Tests (if exist)

Phase 3: Gherkin Verification (Backend - G#N)

3.1 Endpoint Existence

3.2 Response Shape

3.3 Error Handling

Gherkin Checklist

Phase 4: Acceptance Verification (Frontend - AC#N)

4.1 Component Existence

4.2 Storybook Story (if AC involves visual)

4.3 Browser MCP Verification (if running)

Acceptance Checklist

Phase 5: Generate Verification Report

Phase 6: Handle Verdict

GREEN Verdict

RED Verdict - Auto-Invoke Debug

Integration with Debug

MCP Tools Used

Invocation

Files

Compare with similar skills

Similar skills

More from WellApp-ai/Well

Related

Questions about QA Commit