A quality-assurance review command for checking completed work against a project’s testing rules and definition of done, meaning the conditions required to call a ticket finished.

Use `/qa-review` with a ticket number or sprint name to review completed tickets, run the relevant tests, and confirm the expected user flows work.

It matches verification to the kind of change, such as a bug fix, API, user interface, database migration, or documentation update.

How Hundia/autospec configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to Hundia/autospec. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/Hundia/autospec/main/.claude/commands/qa-review.md

Clone the repo

git clone --depth 1 https://github.com/Hundia/autospec

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/hundia/autospec/qa-review.svg)](https://agentmods.dev/commands/hundia/autospec/qa-review)

Your own site

<a href="https://agentmods.dev/commands/hundia/autospec/qa-review"><img src="https://agentmods.dev/badge/commands/hundia/autospec/qa-review.svg" alt="Measured on agentmods" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,010 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 1 finding. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.01010
Opus 5	$0.00000	$0.00505
Sonnet 5	$0.00000	$0.00202
Haiku 4.5	$0.00000	$0.00101

Measured 6d ago against content hash 809b21dd451d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

qa-review scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

| **API change** | Run API tests. If new endpoint, test via curl with happy path + error cases |

.claude/commands/qa-review.md · 136 lines

How it starts

The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.

QA Review

Review completed tickets following the QA Lead guidelines with change-appropriate verification.

Usage

/qa-review [ticket_number or "sprint X"]

Examples:

/qa-review 4.3 - Review single ticket
/qa-review sprint 4 - Review all 🧪 QA Review tickets in Sprint 4

Instructions

When this command is invoked:

Read QA standards:
- Read specs/05_qa_lead.md for quality guidelines
- Read docs/testing/strategy.md for test patterns
- Understand Definition of Done checklist
Identify tickets to review:
- Read specs/backlog.md
- Find tickets with 🧪 QA Review status
- If specific ticket provided, review only that one

Scale QA to change type:

Change Type	QA Required
Bug fix	Reproduce the bug first, apply fix, verify the exact user flow passes
API change	Run API tests. If new endpoint, test via curl with happy path + error cases
UI change	Run UI/component tests. Verify rendering on target viewports
Database migration	Verify migration applies cleanly, test affected API endpoints
Docs/config only	No QA needed — mark ✅ directly
Full-stack feature	Run full test suite. Add test cases if coverage gaps exist

For each ticket, verify:

Code Quality
- Follows project coding standards (docs/project/coding-standards.md)
- No console.log/print statements left
- Error handling implemented
- No hardcoded secrets/URLs
- TypeScript types correct (no any)
Testing
- Unit tests written and pass
- Integration tests if applicable
- Edge cases covered
- Tests are meaningful (not just coverage padding)
Functionality
- Feature works as specified in the linked spec
- Handles error states gracefully
- No regressions to existing features
Security (if applicable)
- Input validation present
- Auth/authz enforced where needed
- No SQL injection, XSS, or CSRF vulnerabilities

Read the full file on GitHub · 136 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

6d ago First seen · 136 lines · 0 tokens per session scan A 809b21dd451d

Subscribe to this mod's changes

qa-review is a command published in the GitHub repository Hundia/autospec (4 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,010 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Testing

qa-changes

This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…

OpenHands/extensions · 63 tokens

autospec: Command for Claude Code

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Makes network callslowCapability

How it starts

QA Review

Usage

Instructions

Code Quality

Testing

Functionality

Security (if applicable)

What this file has done since we first saw it

Other commands, from other repositories

qa-changes

verify

test-coverage

tdd

check-dev

laravel-playwright