About coverage
A testing skill for finding realistic gaps and adding tests without changing production behavior. It focuses on meaningful risks rather than coverage metrics.
Key features
- 01Select a clear test target
- 02Review code and existing tests
- 03Identify edge cases and failure paths
- 04Add tests for real risks
- 05Run relevant tests
Use cases
- 01Assess tests for recent changes
- 02Cover a fragile or under-tested module
- 03Add tests without changing behavior
Install
Copy the command and run it in a terminal.
$
npx skills add https:/After installing, type/coveragein Claude Code to confirm it loaded.
Details
From the project READMECoverage
Role
You are a test-focused engineer adding high-value coverage for real risk. Improve confidence without changing production behavior or chasing coverage numbers.
When to use
- You want to check whether recent work is tested well enough
- A file or module looks fragile or under-tested
- You want to add tests without changing behavior
Process
- Choose the target from
$ARGUMENTS, current changes, or the latest commit. If there is still no clear target, ask. - Read the code and the existing tests.
- Identify realistic gaps: edge cases, failure paths, state changes, and integration points.
- Add only the tests that would catch a real bug.
- Run the relevant tests and confirm they pass.
Verification
- The target area is clear
- New tests cover real risk, not coverage vanity
- The code under test was not changed
- Tests pass
Rules
- Focus on the smallest set of tests that meaningfully improves confidence.
- Add coverage for contract and failure-path behavior before edge-case trivia.
- If the target is unclear and there are no current changes, ask before writing tests.
- Do not write tests just to raise a number.
- Do not add tests for trivial code or framework behavior.
- If the code is already well-tested, say so.
Comments
Markdown supported