test-review
Skill1 starsChanged yesterdayMITView on GitHub
Judge whether a diff is adequately tested, for code review. Runs focused sub-agents one after another (regression, behavior and edge cases, concurrency and race conditions, mutation) and reports findings with proof. Reads and runs, never edits the repo. Use for "review the tests", "are these tests good", "is this tested enough", "mutation test this", "test review", or as the test pass of a PR review.
19 other projects use a version of this.
Adopted by
Most recently taken up by
- getsentry/sentry-godottheir own version, first seen Nov 15, 2026
- oberemokis/skillstheir own version, first seen Nov 15, 2026
- fengzai6/skillstheir own version, first seen Nov 13, 2026
- akovalion/paranoid-qatheir own version, first seen Oct 19, 2026
- ArangoGutierrez/claude-toolkittheir own version, first seen Oct 15, 2026
- Katzeee/agent-foundrytheir own version, first seen Oct 13, 2026
Used with
Projects with it also use test-plan, maintain-verification-skill and 6 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
mbwsimsSkilltest-plan
This skill should be used when the user asks to "plan tests", "what should I test", "what tests do I need", "test plan for", "testing strategy for", "test matrix for", "what cases should I cover", "help me plan tests", mentions "/test-plan", or wants to understand what tests are needed before writing any test code.
Also in 3 projects that use this
jaydubya818Skillmaintain-verification-skill
Use when a project's verification driver or feature map may be stale.
Also in 3 projects that use this
jaydubya818Skillcreate-verification-skill
Use when a repository needs a repeatable driver that proves real UI, CLI, or service behavior.
Also in 3 projects that use this
MicrosoftSkillblast-radius
Assesses network dependency and shared-infrastructure exposure. Use when the user asks which services, customers, SLA policies, routes, or redundant links are affected by a network fault.
Also in 3 projects that use this
asterkinSkilladr
Create Architecture Decision Records (ADRs) following project standards. Guides template usage, process, and best practices for documenting architecturally significant decisions.
Also in 3 projects that use this
AnthropicSkillarchitecture
Create or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.
Also in 3 projects that use this
Other versions19 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 19
- NG-ZORRO/ng-zorro-antd★ 9.2ksame name
- getsentry/sentry-godot★ 260same name
- sd0xdev/sd0x-dev-flow★ 192same name
- sd0xdev/sd0x-harness★ 192same name
- Dimon94/dverity★ 107same name
- Dimon94/skills★ 107same name
- mbwsims/claude-universe★ 71same name
- akovalion/paranoid-qa★ 16same name
- katalon-labs/true-skills★ 10same name
- yasunori0418/skills★ 9same name
9 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository28 other files it gives its agents.
- AGENTS.mdAGENTS.md
- vercel-react-best-practices/AGENTS.mdAGENTS.md
- architecture-reviewSkill
- awsSkill
- code-review-frontendSkill
- comment-sickoSkill
- demo-scriptSkill
- documentation-writerSkill
- dotnetSkill
- factory-reviewSkill
- factorySkill
- lets-talk-about-itSkill
- nextjs-proxy-csp-hardeningSkill
- performance-review-humanizerSkill
- pr-body-styleSkill
- prd-modeSkill
- prove-it-worksSkill
- pythonSkill
- qa-reviewSkill
- reconcile-reviewsSkill
- security-reviewSkill
- simplifySkill
- spikeSkill
- sweSkill
- typescript-strict-styleSkill
- unslopSkill
- vercel-react-best-practicesSkill
- whats-going-onSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 4 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 13 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Never edit, stage, or commit files in the user's checkout.
- Distinctive: line 15
Do not install a tool or dependency without asking.
- Very specific: line 16
Every finding is [ASSUMPTION], VERIFIED (read), or VERIFIED (ran).
- Distinctive: line 17
Do not report style, naming, or test-framework preferences.
- Very specific: line 24
Create the worktree outside the repo: git worktree add --detach <tmp>/test-review-<short-sha> HEAD.
- Very specific: line 25
Create the handoff file .planning/reviews/test-review/<branch>.md in the target project.
- Distinctive: line 29
Run one sub-agent per row, in this order, each only after the previous one has finished.
- Very specific: line 42
Use the Agent tool with subagent_type: general-purpose, in the foreground, one call per row.
- Very specific: line 57
Follow references/report.md.
“Common” is measured: kept by at least 6 in 10 of the 13 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Test Review
Judge the tests that go with a change, not the change itself. The question is: if this diff were wrong, would the tests notice? Each focus is a separate sub-agent. They run in order, and each reads what the earlier ones found.
Guardrails
- Scope is the diff against the base branch. Report only gaps in tests for the lines the diff adds or changes. Do not report missing tests for code the author did not touch.
- Never edit, stage, or commit files in the user's checkout. All runs happen in a throwaway git worktree.
- Throwaway tests are allowed inside the worktree to prove a gap. Never present them as the author's tests.
- Do not install a tool or dependency without asking. If a tool is missing, say so and use the fallback in the focus reference.
- Every finding is
[ASSUMPTION],VERIFIED (read), orVERIFIED (ran). AVERIFIED (ran)finding quotes the command and its output. Omit a finding you cannot support at the first tier. - Do not report style, naming, or test-framework preferences.
- This skill does not fix anything. A gap comes with a one-sentence description of the test that would close it.
Setup
- Resolve the base branch:
git symbolic-ref --short refs/remotes/origin/HEAD, falling back toorigin/main. If the branch is the base branch or the diff is empty, say "Nothing to review" and stop. - Get the diff with
git diff <base>...HEAD. If it cannot be obtained, stop and ask. - Create the worktree outside the repo:
git worktree add --detach <tmp>/test-review-<short-sha> HEAD. Remove it at the end. - Create the handoff file
.planning/reviews/test-review/<branch>.mdin the target project. Create the directory if needed.
Pipeline
Run one sub-agent per row, in this order, each only after the previous one has finished. Never start two at once. Skip a row only when Scope says it does not apply, and record the skip and the reason in the handoff file.
| # | Focus | Question it answers | Read |
| 1 | Scope | What changed, which test runner and tools exist, which focuses apply? | references/scope.md |
| 2 | Regression | Does something that worked before now depend on a changed line without a test pinning it? Does a bug-fix test fail on the old code? | references/regression.md |
| 3 | Behavior | Do the tests assert what a caller can observe, including edge and failure cases? | references/behavior.md |
| 4 | Concurrency | Can the changed code race, reorder, or deadlock, and does any test force it? Are the changed tests flaky? | references/concurrency.md |
| 5 | Mutation | If the changed code were subtly wrong, would any test fail? | references/mutation.md |
| 6 | Report | What is the verdict? | references/report.md |
How to spawn each stage
Use the Agent tool with subagent_type: general-purpose, in the foreground, one call per row. Give every stage a standalone brief with:
- the goal: "Judge whether this diff is adequately tested, for code review",
- the base branch, the worktree path, and the handoff file path,
- the focus reference to read and follow,
- the rule that it reads the handoff file first and appends its own section, and does not rewrite earlier sections,
- the guardrails above, repeated in full,
- the report format: each finding has a severity,
file:line, evidence tier, the gap, and the test that would close it.
Read the handoff file after each stage. If a stage's section is missing, or a finding cites a line that is not in the diff, send the stage back once with the problem named. After a second miss, record a gap and continue. A gap is not a pass.
You own the result. Do not paste a stage's output into the report without checking that its cited lines exist.
Output
Follow references/report.md. In short:
- A verdict:
APPROVE,REQUEST TESTS, orBLOCK. - Findings ordered by severity, each tied to a changed line, with its evidence tier and the test that would close it.
- A table of stages with their status: ran, skipped (with reason), or gap.
- What was not tested or not run, every time.
Durable output stays under .planning/reviews/test-review/ in the target project, never in this repo.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

