/coverage
Analyze test coverage gaps. Use when user says "test coverage", "what's not tested", "coverage gaps", "missing tests", "coverage report", or "what needs testing".
One skill from claude-skills.
shell
$ npx -y skills add alirezarezvani/claude-skills --skill coverage --agent claude-codeInstalls just this skill. Get the whole plugin for auto-invocation.
How it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/coverage
Context preview
The summary Claude sees to decide when to auto-load this skill.
Analyze test coverage gaps. Use when user says "test coverage", "what's not tested", "coverage gaps", "missing tests", "coverage report", or "what needs testing".
Stats
Stars23,060
Forks3,139
LanguagePython
LicenseMIT
Ships with claude-skills
SKILL.md
coverage.SKILL.md
--- name: "coverage" description: >- Analyze test coverage gaps. Use when user says "test coverage", "what's not tested", "coverage gaps", "missing tests", "coverage report", or "what needs testing". --- # Analyze Test Coverage Gaps Map all testable surfaces in the application and identify what's tested vs. what's missing. ## Steps ### 1. Map Application Surface Use the `Explore` subagent to catalog: **Routes/Pages:** - Scan route definitions (Next.js `app/`, React Router config, Vue Router, etc.) - List all user-facing pages with their paths **Components:** - Identify interactive components (forms, modals, dropdowns, tables) - Note components with complex state logic **API Endpoints:** - Scan API route files or backend controllers - List all endpoints with their methods **User Flows:** - Identify critical paths: auth, checkout, onboarding, core features - Map multi-step workflows ### 2. Map Existing Tests Scan all `*.spec.ts` / `*.spec.js` files:
