Individual skill
test-coverage-analyzer
Identifies which behaviors are meaningfully untested and risk-ranks the gaps, rather than reporting line-coverage percentage. Use when deciding where to add tests next.
skills/testing/test-coverage-analyzer/SKILL.md
Source commit d0a9928d24afb7df0fad2f2f35f65d3938a6926a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 27
- Repository last updated
- Aug 20, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-code Repository topic
- ai Repository topic
- ai-agents Repository topic
- ai-coding Repository topic
- ai-skill Repository topic
- ai-skill-enhancement Repository topic
- ai-skills Repository topic
- ai-skills-analysis Repository topic
- ai-skills-fest Repository topic
- ai-skills-manager Repository topic
- testing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
README.mddoc · 1,281 bytesSKILL.mdcore · 2,562 bytesexamples/example.mddoc · 3,200 bytes
Read excerpt
## Purpose
Find the testing gaps that actually matter — untested *behaviors* weighted by risk — instead of chasing a line-coverage percentage that can be high while the important paths remain unverified.
## When to Use
- Deciding where to invest limited testing effort next.
- Coverage numbers look acceptable but bugs keep escaping to production.
- Before modifying risky code, to find out what's currently protecting it (and what isn't).
Differs from [Test Generator](../test-generator/): that writes tests; this decides *which* tests are worth writing first.
## What to Analyze