coverage-gaps

Name: coverage-gaps
Author: Archive228

712stars129forks

How to install coverage-gaps?

archive228/loopkit/coverage-gaps

$npx -y skills add Archive228/loopkit --skill coverage-gaps

Installs into the current project.

Summary

Find the untested code paths that actually matter, not just the coverage percentage. Use after adding tests.

Files · 1

SKILL.md

1	# Coverage Gaps
2	Coverage % is a vanity metric. Hunt the gaps that bite:
3	- Error paths — the 500, the timeout, the empty/null input, the malformed payload. Almost always untested.
4	- Boundaries — 0, 1, max, off-by-one, empty collection.
5	- Branches — every `if/else` and `catch` exercised, not just the happy line.
6	- Concurrency / order — anything stateful tested in isolation AND in sequence.
7	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.

6 picks

Type

1	# Coverage Gaps
2	Coverage % is a vanity metric. Hunt the gaps that bite:
3	- Error paths — the 500, the timeout, the empty/null input, the malformed payload. Almost always untested.
4	- Boundaries — 0, 1, max, off-by-one, empty collection.
5	- Branches — every `if/else` and `catch` exercised, not just the happy line.
6	- Concurrency / order — anything stateful tested in isolation AND in sequence.
7	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.

1	# Coverage Gaps
2	Coverage % is a vanity metric. Hunt the gaps that bite:
3	- Error paths — the 500, the timeout, the empty/null input, the malformed payload. Almost always untested.
4	- Boundaries — 0, 1, max, off-by-one, empty collection.
5	- Branches — every `if/else` and `catch` exercised, not just the happy line.
6	- Concurrency / order — anything stateful tested in isolation AND in sequence.
7	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.