coverage-gaps
Skill0 starsChanged 5 days agoMITView on GitHub
Ranks the most valuable missing tests from coverage.py's coverage.json. Use when the user asks which tests are missing. Not for non-Python code.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- telerik/observability-skillstheir own version, first seen Oct 22, 2026
- microsoft/aibast-agents-librarytheir own version, first seen Oct 13, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- microsoft/aibast-agents-library★ 8same name
- telerik/observability-skills★ 1same 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 repository22 other files it gives its agents.
- AGENTS.mdAGENTS.md
- claude-arsenal/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- dep-upgradeSkill
- designSkill
- executionSkill
- explore-ideaSkill
- gate-checkSkill
- githubSkill
- initSkill
- litcriticSkill
- mutmut-reportSkill
- pin-checkSkill
- pypi-releaseSkill
- python-bootstrapSkill
- queue-addSkill
- queue-nextSkill
- queue-statusSkill
- reviewSkill
- session-endSkill
- shipSkill
- specifySkill
The file
Files
coverage-gaps
Turns an existing coverage.py report into a ranked list of the tests worth writing next.
CANARY: coverage-gaps-loaded-2026-06-04-ea39c2b5-b32fe2b1b5ae5e96
When to load
Load when the question is which coverage gaps to fill first. This is the cheap,
line-level pass; once line coverage is healthy and the question is whether
tests assert behaviour, use the mutmut-report skill.
Step 1 — Ensure a JSON report exists
The script reads coverage.py's JSON export, not the .coverage database, and
exits 2 without it. Regenerate it after a refactor, since old line numbers
drift from the source.
coverage json # after `coverage run -m pytest`
pytest --cov=PKG --cov-branch --cov-report=json # or in one shot, with branchesStep 2 — Rank the gaps
python3 "${CLAUDE_SKILL_DIR}/scripts/analyze_coverage.py" --input coverage.json --limit 20The JSON carries total_percent_covered, files_with_gaps, and a ranked gaps
list with missing_count, percent_covered, missing_branches (populated only
with branch coverage), largest_run and missing_runs (inclusive line ranges).
Step 3 — Propose tests
Open the source at each missing_runs range before recommending, because a long
run can be a generated block, a __repr__ or an if TYPE_CHECKING: island;
rank by what the code does, not by line count. Then report:
- The 2–3 tests worth writing now: which function, which input, which branch.
- Branch gaps in otherwise well-covered files, from
missing_branches. - Low-value gaps (scattered defensive
raiseor logging lines) that can wait or take# pragma: no cover.
Covered means executed, not asserted, so treat this ranking as the floor.
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.

