test-gap-audit
Skill0 starsChanged 24 days agoMITView on GitHub
Review existing test coverage for important behavior, missing assertions, and false confidence without changing code. Use to assess a test suite; not to implement new tests.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- docdyhr/simplenote-mcp-servertheir own version, first seen Nov 1, 2026
- github/awesome-copilottheir own version, first seen Oct 25, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- github/awesome-copilot★ 41ksame name
- docdyhr/simplenote-mcp-server★ 21same 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 repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- acceptance-qaSkill
- architecture-reviewSkill
- bug-fix-verificationSkill
- dependency-upgradeSkill
- docs-syncSkill
- idea-to-scopeSkill
- implementation-planSkill
- independent-reviewSkill
- migration-safetySkill
- performance-investigationSkill
- pull-request-handoffSkill
- release-checkpointSkill
- root-cause-investigationSkill
- security-reviewSkill
- surgical-changeSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
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
Look for gaps: a successful path without failure checks, missing negative cases, brittle snapshots, shared test pollution, unverifiable …
- Distinctive: line 14
If running tests might write snapshots, fixtures, caches, or project files, use a disposable copy.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Test-gap audit
Coverage percentages are a map, not the destination. This is a read-only audit.
- Identify the behavior and regression surface. Read tests alongside the production paths they claim to exercise.
- Trace meaningful boundaries: validation, authorization, failure handling, persistence, concurrency, and public contracts where relevant.
- Inspect assertions, test doubles, fixtures, and setup. Ask whether the test fails for the relevant defect or merely proves the mock was configured.
- Look for gaps: a successful path without failure checks, missing negative cases, brittle snapshots, shared test pollution, unverifiable external assumptions, and tests that cannot detect regressions.
- If running tests might write snapshots, fixtures, caches, or project files, use a disposable copy. Do not run auto-fix or coverage instrumentation that mutates the reviewed target.
- Rank a short list by impact × likelihood × detectability. Suggest the narrowest high-value addition without implementing it.
Output
| Gap | Why existing tests miss it | Suggested assertion or scenario | Priority |
Include target/version, checks actually run, and limitations. Do not infer all behaviors are covered because a test run is green.
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.