test-coverage-review
Skill1 starsChanged 7 months agoMITView on GitHub
Review the test suite of a class in the project and identify missing test cases. Use this skill after writing tests or when the user asks for a coverage review.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- Smaui94/ClaudeSkillCollectiontheir own version, first seen Nov 8, 2026
- Ronnasayd/aipptheir own version, first seen Oct 20, 2026
- NoRiceToday/skillstheir own version, first seen Oct 2, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- NoRiceToday/skills★ 1same name
- Ronnasayd/aipp★ 1same name
- Smaui94/ClaudeSkillCollection★ 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 repository12 other files it gives its agents.
- api-consistency-checkSkill
- architecture-drift-checkSkill
- design-reviewSkill
- jml-completeness-checkSkill
- jml-conformance-checkSkill
- jml-designSkill
- jml-test-generationSkill
- new-classSkill
- refactor-classSkill
- static-analysisSkill
- update-backlogSkill
- update-readmeSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
4
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 13
After writing black-box and white-box tests
- Distinctive: line 14
Before marking a backlog task as done
- Distinctive: line 15
When the user says "review the tests" or "is the test coverage sufficient"
- Distinctive: line 59
If no issues are found in a category, skip it entirely.
“Common” is measured: kept by at least 6 in 10 of the 3 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 Coverage Review
When to run
- After writing black-box and white-box tests
- Before marking a backlog task as done
- When the user says "review the tests" or "is the test coverage sufficient"
Coverage checklist
1. Public API coverage
- Every public method has at least one test
- Both nominal and error cases are tested
- Boundary cases covered (empty, single element, null where applicable)
2. Behavioural coverage
- Tests verify observable behaviour rather than implementation details
- Contract of the implemented interface respected
3. Mutation scenarios
- Add / remove operations tested
- Structure integrity verified after mutations
- Sequences of operations tested
4. Edge cases
- Empty structure behaviour
- Large structure behaviour
- Boundary values
5. White-box coverage
- Internal edge cases tested
- Resize / rehash boundaries tested
- Collision scenarios tested where applicable
Output format
Report findings grouped by category. For each finding, state:
- The method or scenario not covered
- The recommended test
- The test level (black-box or white-box)
If no issues are found in a category, skip it entirely.
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.