test-review
Skill0 starsChanged 4 months agoNo licenceView on GitHub
Review test value, design, and coverage trade-offs. Use when deciding whether implementation work needs tests, when adding, modifying, or removing tests or test support, when changing test execution settings, or when reviewing an existing test suite.
16 other projects use a version of this.
Adopted by
Most recently taken up by
- fengzai6/skillstheir own version, first seen Nov 3, 2026
- akovalion/paranoid-qatheir own version, first seen Oct 19, 2026
- ArangoGutierrez/claude-toolkittheir own version, first seen Oct 15, 2026
- Dimon94/skillstheir own version, first seen Oct 13, 2026
- Dimon94/dveritytheir own version, first seen Oct 13, 2026
- tslateman/skillstheir own version, first seen Oct 11, 2026
Used with
Projects with it also use test-plan, maintain-verification-skill and 7 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.
mbwsimsSkilltest-plan
This skill should be used when the user asks to "plan tests", "what should I test", "what tests do I need", "test plan for", "testing strategy for", "test matrix for", "what cases should I cover", "help me plan tests", mentions "/test-plan", or wants to understand what tests are needed before writing any test code.
Also in 3 projects that use this
jaydubya818Skillmaintain-verification-skill
Use when a project's verification driver or feature map may be stale.
Also in 3 projects that use this
jaydubya818Skillcreate-verification-skill
Use when a repository needs a repeatable driver that proves real UI, CLI, or service behavior.
Also in 3 projects that use this
MicrosoftSkillblast-radius
Assesses network dependency and shared-infrastructure exposure. Use when the user asks which services, customers, SLA policies, routes, or redundant links are affected by a network fault.
Also in 3 projects that use this
asterkinSkilladr
Create Architecture Decision Records (ADRs) following project standards. Guides template usage, process, and best practices for documenting architecturally significant decisions.
Also in 3 projects that use this
AnthropicSkillarchitecture
Create or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.
Also in 3 projects that use this
Other versions16 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 16
- NG-ZORRO/ng-zorro-antd★ 9.2ksame name
- sd0xdev/sd0x-dev-flow★ 192same name
- sd0xdev/sd0x-harness★ 192same name
- Dimon94/dverity★ 107same name
- Dimon94/skills★ 107same name
- mbwsims/claude-universe★ 71same name
- akovalion/paranoid-qa★ 16same name
- katalon-labs/true-skills★ 10same name
- yasunori0418/skills★ 9same name
- ArangoGutierrez/claude-toolkit★ 4same name
6 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 repository7 other files it gives its agents.
- configure-agent-guidanceSkill
- domain-modelingSkill
- handoffSkill
- refactor-refereeSkill
- spikeSkill
- to-goalSkill
- wayfinderSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 11 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.
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.

