test-design
Skill2 starsChanged 3 months agoMITView on GitHub
Draft executable test cases from approved requirements plus the OpenAPI spec. One invocation per endpoint.
23 other projects use a version of this.
Adopted by
Most recently taken up by
- jame-hv/brse-toolkittheir own version, first seen Nov 16, 2026
- LeanMeanCleanApps/CleanLambdaFunctiontheir own version, first seen Nov 15, 2026
- LeanMeanCleanApps/CleanWebApitheir own version, first seen Nov 15, 2026
- LeanMeanCleanApps/CleanGraphQLApitheir own version, first seen Nov 15, 2026
- LeanMeanCleanApps/CleanMinimalApitheir own version, first seen Nov 15, 2026
- selamy-labs/agent-skillstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use diff-review.
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.
MidnightDarlingSkilldiff-review
使用场景:按 raw.review.md 清单改完稿后,对 raw.md(OCR 原始)和 final.md(定稿)做对比。说"看我改了哪些""对比一下""diff""校对完了让我看看""我到底接受了哪些建议""我漏改了啥""改动统计""核对一下改动""闭环检查"都走这个 skill。生成段落级 HTML diff,关联 raw.review.md 的 A/B/C 标注,一目了然:接受了哪些 agent 建议、拒绝了哪些、清单外修正了哪些、agent 标过但漏改了哪些。主动触发,不必等用户说 "diff-review"。
Also in 3 projects that use this
Other versions23 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 23
- Agenta-AI/agenta★ 4.9ksame name
- LeanMeanCleanApps/CleanMinimalApi★ 400same name
- adamentwistle/fable-skills★ 98same name
- nahid-sparktales/agent-dispatcher★ 59same name
- LeanMeanCleanApps/CleanGraphQLApi★ 13same name
- shabaraba/vibing.nvim★ 13same name
- tlzmw001/aitest-kit★ 13same name
- yasunori0418/skills★ 9same name
- umararshad4/honey-stack★ 5same name
- LeanMeanCleanApps/CleanWebApi★ 4same name
13 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 repository3 other files it gives its agents.
- requirements-authoringSkill
- requirements-reviewSkill
- test-case-reviewSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 17 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Every case exists to exercise a requirement — if you cannot name the requirement, do not write the case.
- Very specific: line 16
Every case links to at least one approved req_id via requirement_ids.
“Common” is measured: kept by at least 6 in 10 of the 17 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 Design
Draft test cases for one endpoint from its approved requirements and the spec.
Requirements say what must hold; a test case says how you would demonstrate it. Every case exists to exercise a requirement — if you cannot name the requirement, do not write the case.
Rules
- Every case links to at least one approved
req_idviarequirement_ids. - Cover every approved requirement with at least one case. An uncovered requirement is a gap the traceability check will report.
expected_statusmust be a status code the spec declares for this operation. This is enforced; a status the spec does not declare is rejected.categorymust be one of happy_path, negative, boundary, auth, security, and must have been requested for this run. Also enforced.- Inputs —
path_params,query_params,headers,body— must be valid per the spec: real parameter names, real types, required fields present. A negative case breaks exactly one rule on purpose and states which. expected_bodyholds assertions in the grammar below, one claim per entry. Prose is not compiled into the generated test — it survives only as a TODO comment a human has to finish, so an assertion you can express in the grammar is worth far more than one you cannot.test_data_notessays what real data the operator must supply — "a petId that exists in the store", not "user provides data".preconditionsare things that must be true before the request, not steps.- Priority inherits from the requirement unless the case is a narrower edge of it.
Assertion grammar
expected_body entries must be one of these six forms. $. addresses the
response body; $.a.b[0].c walks nested objects and arrays.
$.path == value $.id == 5 $.name == 'Fluffy'
$.path != value $.code != 500
$.path contains 'text' $.message contains 'required'
$.path exists $.id exists
$.path matches /regex/ $.name matches /^[A-Z]/
$.array length == N $.tags length == 2Assert what the spec's response schema actually promises. Do not assert on a field the schema does not declare.
IDs
case_id is TC-<OPTOKEN>-<NNN>, numbered from 001 within this endpoint, using
the OPTOKEN given to you. Duplicate IDs within a run are rejected.
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.

