test-generation
Skill2 starsChanged 5 months agoMITView on GitHub
Generate a test strategy and starter test stubs for given modules across unit, integration, and e2e layers (pytest/jest/playwright). Trigger on: generate tests, test plan, test strategy, coverage plan, test scaffolding.
9 other projects use a version of this.
Adopted by
Most recently taken up by
- alexuraxin/retainertheir own version, first seen Nov 15, 2026
- Happy-Technologies-LLC/happy-platform-skillstheir own version, first seen Nov 1, 2026
- okfriansyah-moh/agentic-workflowtheir own version, first seen Oct 25, 2026
- int2t05/engineering-skillstheir own version, first seen Oct 15, 2026
- jnotsknab/mux-swarmtheir own version, first seen Oct 11, 2026
- EmeaAppGbb/spec2cloudtheir own version, first seen Oct 9, 2026
Used with
Projects with it also use debugging, frontend-design and 1 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.
BlockSkilldebugging
Debugging guidelines and best practices
Also in 3 projects that use this
- BlockSkill
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
Also in 3 projects that use this
GoogleSkillcode-review
Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.
Also in 3 projects that use this
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- EmeaAppGbb/spec2cloud★ 100same name
- Happy-Technologies-LLC/happy-platform-skills★ 41same name
- jnotsknab/mux-swarm★ 9same name
- crgarcia12/Liliput★ 4same name
- alexuraxin/retainer★ 3same name
- int2t05/engineering-skills★ 3same name
- Anasabdellatif/forgeos★ 2same name
- Bridev04/clauderail★ 0same name
- okfriansyah-moh/agentic-workflow★ 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 repository15 other files it gives its agents.
- change-impact-analysisSkill
- legacy-discoverySkill
- spec-governanceSkill
- task-decompositionSkill
- topology-planningSkill
- ui-modernizationSkill
- jira-ticketSkill
- servicenow-ticketSkill
- speckit-constitutionSkill
- speckit-planSkill
- speckit-specifySkill
- speckit-tasksSkill
- my-skillSkill
- text-statisticsSkill
- xquik-social-dataSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 43
When establishing or improving test coverage.
“Common” is measured: kept by at least 6 in 10 of the 9 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-generation
Produce a layered test strategy (unit/integration/e2e) and starter stubs for the given modules across pytest, jest, and playwright.
When to use
When establishing or improving test coverage. Triggers: generate tests, test plan, coverage plan, test scaffolding.
Inputs
modules(array of strings, required).frameworks(array, optional, default[pytest, jest, playwright]).
Outputs
test_plan_markdown— pyramid, coverage matrix, targets.stubs— starter tests per module per framework.
How it works
Builds a coverage matrix for the modules and emits idiomatic stubs per requested
framework from the templates in jest_templates/ and playwright_templates/.
User stories
- As an engineer, I get a coverage plan and runnable stubs to fill in.
Edge cases
- A single module string is accepted.
- Empty modules → clear error.
- Unknown frameworks are ignored gracefully.
Files
See DOCS.md.
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.