test-cases
Skill224 starsChanged 3 months agoMITView on GitHub
Generate test cases from use cases, update when requirements change, export to CSV/JSON.
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
0
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
- Very specific: line 13
If invoked without arguments, use AskUserQuestion to present available operations:
“Common” is measured: kept by at least 6 in 10 of the 10 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 Case Management
Generate, update, and export test cases from use case documentation.
Default (No Arguments)
If invoked without arguments, use AskUserQuestion to present available operations:
| Operation | Description |
generate | Generate test cases from use cases |
update | Sync test cases with use case changes |
export | Export test cases to CSV or JSON |
Present as options via AskUserQuestion with header "Test Case Management", question "What would you like to do?".
Subcommands
| Subcommand | Reference | Purpose |
/test-cases generate | references/generate-workflow.md | Generate TCs for all use cases |
/test-cases generate {module} | references/generate-workflow.md | Generate TCs for specific module |
/test-cases generate {module}/{uc} | references/generate-workflow.md | Generate TCs for specific use case |
/test-cases update | references/update-workflow.md | Sync TCs with use case changes |
/test-cases export csv | references/export-workflow.md | Export all TCs to CSV |
/test-cases export json | references/export-workflow.md | Export all TCs to JSON |
Routing
Parse $ARGUMENTS:
- Starts with
generate→ Loadreferences/generate-workflow.md, pass remaining args as scope update→ Loadreferences/update-workflow.md- Starts with
export→ Loadreferences/export-workflow.md, pass format (csv/json) as arg - empty/unclear → AskUserQuestion
Shared Context
- TC template:
references/templates/test-case-template.md - Summary template:
references/templates/test-summary-template.md - Input UCs:
docs/usecases/{module}/*.md - Input FSD:
docs/project-fsd.md - Output TCs:
docs/testcases/{module}/tc-{module}-{nnn}-{slug}.md - Output summary:
docs/testcases/test-summary.md - Output config:
docs/testcases/test-config.md(created once on first generate, manually maintained after) - Config template:
references/templates/test-config-template.md - Output exports:
docs/testcases/export/
IMPORTANT: Do not start implementing code. This skill produces test case documentation only.
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- cexll/myclaude★ 2.8ksame name
- ssdeanx/AgentStack★ 44same name
- spmtitsolution/OpenBA-Kit★ 38same name
- akovalion/paranoid-qa★ 16same name
- ieuanign/skills★ 2same name
- mateodiazvaldez/skills★ 1same name
- raditia/CraftKit★ 1same name
- gr219/OpenBA-Kit★ 0same name
- latuconsinafr/claude-code-config★ 0same name
- sueryue/Claude-Skillls★ 0same 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 repository46 other files it gives its agents.
- .claude/skills/react-best-practices/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- ai-multimodalSkill
- askSkill
- backend-developmentSkill
- brainstorm-featuresSkill
- brainstorm-technicalSkill
- chrome-devtoolsSkill
- code-reviewSkill
- context-engineeringSkill
- cookSkill
- databasesSkill
- debugSkill
- design-mockup-createSkill
- design-systemSkill
- devopsSkill
- docs-seekerSkill
- docsSkill
- fixSkill
- frontend-designSkill
- frontend-developmentSkill
- gitSkill
- journalSkill
- markdown-novel-viewerSkill
- mermaidjs-v11Skill
- mobile-developmentSkill
- plans-kanbanSkill
- planSkill
- previewSkill
- problem-solvingSkill
- project-managementSkill
- quality-gatesSkill
- react-best-practicesSkill
- repomixSkill
- researchSkill
- scoutSkill
- sequential-thinkingSkill
- skill-creatorSkill
- specsSkill
- teamSkill
- testSkill
- ui-stylingSkill
- ui-ux-pro-maxSkill
- web-design-guidelinesSkill
- web-frameworksSkill
- web-testingSkill
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.