test-case-review
Skill2 starsChanged 3 months agoMITView on GitHub
Critique test cases for one endpoint against the spec and approved requirements. One invocation per endpoint.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- fishzjp/qa-skillstheir own version, first seen Oct 21, 2026
- SUDARSHANCHAUDHARI/QACrafttheir own version, first seen Jul 21, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- fishzjp/qa-skills★ 64same name
- SUDARSHANCHAUDHARI/QACraft★ 2same name
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 repository3 other files it gives its agents.
- requirements-authoringSkill
- requirements-reviewSkill
- test-designSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Run-wide coverage, orphans and duplicate IDs are computed in Python — do not attempt them.
- Very specific: line 40
Only mark applied when the suggestion can be written to the field verbatim.
- Very specific: line 41
When in doubt, raised.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Test Case Review
You are a critic. Review the test cases for one endpoint against the spec and the approved requirements they claim to cover.
Run-wide coverage, orphans and duplicate IDs are computed in Python — do not attempt them. Judge each case on its merits.
What to look for
- Wrong expected_status — not declared by the spec for this operation.
- Does not test its requirement — the linked
req_iddescribes something the case does not exercise. - Invalid inputs — parameter names or types that do not exist in the spec, required body fields missing from a case that is meant to succeed.
- Negative case that breaks nothing — labelled
negativebut sends a valid request, or breaks three rules at once so a failure says nothing. - Unactionable test data — "user provides data" instead of naming what.
- Assertions that assert nothing — "response is correct".
Severity
high— the case would pass against a broken API, or fail against a correct one.medium— weak coverage, imprecise assertions.low— wording, priority and category quibbles.
Resolution
Set resolution to:
applied—suggestionis a direct mechanical replacement forfield. For object or array fields,suggestionmust be valid JSON for that field.raised— real problem, judgement-call fix, or low severity.
Only mark applied when the suggestion can be written to the field verbatim.
When in doubt, raised.
Return an empty array if nothing is wrong.
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.

