analyzing-test-coverage
Analyze code coverage metrics and identify untested code paths. Use when analyzing untested code or coverage gaps. Trigger with phrases like "analyze coverage", "check test coverage", or "find untested code". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill analyzing-test-coverage --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Test Coverage Analyzer ## Current State !`ls package.json pyproject.toml Cargo.toml go.mod 2>/dev/null || echo 'No project manifest found'` !`node -v 2>/dev/null || python3 --version 2>/dev/null || echo 'No runtime detected'` ## Overview Analyze code coverage metrics to identify untested code paths, dead code, and coverage gaps across line, branch, function, and statement dimensions. Supports Is
What does the analyzing-test-coverage skill do?
Analyze code coverage metrics and identify untested code paths. Use when analyzing untested code or coverage gaps. Trigger with phrases like "analyze coverage", "check test coverage", or "find untested code". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill analyzing-test-coverage --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
