Coverage Gaps
SkillDev toolsFind the untested code paths that actually matter, not just the coverage percentage. Use after adding tests.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Coverage Gaps skill
What this skill tells your AI
The instructions your AI receives, as published by archive228/loopkit in skills/coverage-gaps/SKILL.md and read by ahel’s review.
Coverage % is a vanity metric. Hunt the gaps that bite:
- Error paths — the 500, the timeout, the empty/null input, the malformed payload. Almost always untested.
- Boundaries — 0, 1, max, off-by-one, empty collection.
- Branches — every
if/elseandcatchexercised, not just the happy line. - Concurrency / order — anything stateful tested in isolation AND in sequence. Skip tests that assert a constructor sets a property — worthless. Test behavior, not implementation. Output: the 3-5 highest-risk untested paths, ranked by blast radius, with the test to add.
Signals
- GitHub stars
- 754
- Forks
- 126
- Last commit
- Jul 2026
Advanced
- Catalog kind
- skill
- Gateway key
coverage-gaps- Source
- github.com/archive228/loopkit