test-cases
Skill0 starsChanged 17 days agoMITView on GitHub
Generate a complete set of test cases from a requirement, user story, screenshot, or feature description. Covers positive, negative, boundary, and edge cases, and validates its own output with a script. Use when the user asks to write, design, or generate test cases or test scenarios.
12 other projects use a version of this.
Adopted by
Most recently taken up by
- alexpalexpinne/qa-toolkittheir own version, first seen Nov 8, 2026
- gr219/OpenBA-Kittheir own version, first seen Oct 25, 2026
- spmtitsolution/OpenBA-Kittheir own version, first seen Oct 20, 2026
- akovalion/paranoid-qatheir own version, first seen Oct 19, 2026
- mateodiazvaldez/skillstheir own version, first seen Oct 17, 2026
- ieuanign/skillstheir own version, first seen Oct 13, 2026
Used with
Projects with it also use preview, ask and 3 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.
kv0906Skillpreview
Render vault notes as styled HTML and open in browser. Turn markdown docs, decisions, progress reports into readable previews. Use for "/preview docs/project-a/checkout-flow.md", "/preview progress all", "/preview decide auth-approach", or when user wants to see a doc before sharing.
Also in 3 projects that use this
dubwoahSkillask
Answer questions about the codebase without generating or modifying any code. Use when the user wants to understand how something works, find where something is defined, or explore the project structure. Invoked with /ask.
Also in 3 projects that use this
AnthropicSkilldebug
Structured debugging session — reproduce, isolate, diagnose, and fix. Trigger with an error message or stack trace, "this works in staging but not prod", "something broke after the deploy", or when behavior diverges from expected and the cause isn't obvious.
Also in 3 projects that use this
BlockSkillplan
Draft a TDD, PRD, or lightweight plan in the conversation without committing it.
Also in 3 projects that use this
NVIDIASkillresearch
Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.
Also in 3 projects that use this
Other versions12 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 12
- cexll/myclaude★ 2.8ksame name
- typv/nest-turbo-starter★ 224same 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
- alexpalexpinne/qa-toolkit★ 0same name
- gr219/OpenBA-Kit★ 0same name
2 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 repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- api-testSkill
- automateSkill
- bug-reportSkill
- exploratorySkill
- mobile-testSkill
- test-dataSkill
- test-planSkill
- test-reportSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 12 edited versions we read keep these.
1
Distinctive
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 12
Understand the input: If the requirement is missing key facts (expected behavior, user roles, field limits), ask 1-2 short questions.
- Very specific: line 36
If the validator prints any ERROR, fix the file and run it again.
- Very specific: line 40
If the user asks for CSV/Excel/TestRail format, first produce and validate the markdown version, then convert.
“Common” is measured: kept by at least 6 in 10 of the 12 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 Generator
You are helping a QA tester design test cases. Follow this workflow EXACTLY — do not skip steps.
Workflow (mandatory)
- Understand the input. If the requirement is missing key facts (expected behavior, user roles, field limits), ask 1-2 short questions. Otherwise proceed.
- List the testable behaviors first as a short bullet list (this is your checklist — every behavior must get test cases).
- Write the test cases to a file named
test-cases/<feature-name>.mdusing EXACTLY this table format — same columns, same order, nothing added or removed:
| ID | Category | Title | Preconditions | Steps | Test Data | Expected Result | Priority |
|---|---|---|---|---|---|---|---|
| TC-001 | Positive | Login succeeds with valid credentials | User account exists and is active | 1. Open login page<br>2. Enter valid email<br>3. Enter valid password<br>4. Click Login | user1@test.com / Pass123! | User lands on dashboard; welcome message shows the user's name | P1 |Rules for each cell:
- ID:
TC-001,TC-002, ... sequential, no duplicates. - Category: exactly one of
Positive,Negative,Boundary,Edge,Non-functional. - Steps: numbered
1. 2. 3., separated with<br>inside the cell. Precise enough that a junior tester needs zero questions. - Expected Result: the exact observable outcome. NEVER "works", "success", "no error".
- Priority:
P1(critical) /P2(major) /P3(minor). - Required coverage: at least one
Positive, oneNegative, oneBoundarycase. AddEdgecases (interruption, concurrency, unicode/Arabic text, double-submit) whenever the feature has input or state.
- Validate your output (MANDATORY):
python .claude/skills/test-cases/scripts/validate_test_cases.py test-cases/<feature-name>.mdIf the validator prints any ERROR, fix the file and run it again. Repeat until it prints OK. Never show the user an unvalidated file.
- Finish by showing the user: the coverage counts the validator printed, plus a short "Coverage gaps / questions for the team" section listing anything ambiguous in the requirement.
If the user asks for CSV/Excel/TestRail format, first produce and validate the markdown version, then convert.
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.

