Analyze test coverage gaps. Use when user says "test coverage", "what's not tested", "coverage gaps", "missing tests", "coverage report", or "what needs testing".
npx claudepluginhub alirezarezvani/claude-skillsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Map all testable surfaces in the application and identify what's tested vs. what's missing.
Use the Explore subagent to catalog:
Routes/Pages:
app/, React Router config, Vue Router, etc.)Components:
API Endpoints:
User Flows:
Scan all *.spec.ts / *.spec.js files:
page.goto() calls)## Coverage Matrix
| Area | Route | Tests | Status |
|---|---|---|---|
| Auth | /login | 5 | ✅ Covered |
| Auth | /register | 0 | ❌ Missing |
| Auth | /forgot-password | 0 | ❌ Missing |
| Dashboard | /dashboard | 3 | ⚠️ Partial (no error states) |
| Settings | /settings | 0 | ❌ Missing |
| Checkout | /checkout | 8 | ✅ Covered |
Rank uncovered areas by business impact:
For each gap, recommend:
templates/ to use## Recommended Test Plan
### Priority 1: Critical
1. /register (4 tests) — use auth/registration template — quick
2. /forgot-password (3 tests) — use auth/password-reset template — quick
### Priority 2: High
3. /settings (4 tests) — use settings/ templates — medium
4. Dashboard error states (2 tests) — use dashboard/data-loading template — quick
Ask user: "Generate tests for the top N gaps? [Yes/No/Pick specific]"
If yes, invoke /pw:generate for each gap with the recommended template.