Coverage

Skill sinhoneyy/master-skills/skills/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".From its SKILL.md

Install

npx -y skills add sinhoneyy/master-skills --skill coverage

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
10 stars10 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.7 KB, 634 tokens by cl100k_base, as published. Nobody here has run it

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:

Extract which pages/routes are covered (by page.goto() calls)
Extract which components are tested (by locator usage)
Extract which API endpoints are mocked or hit
Count tests per area

3. Generate Coverage Matrix

## 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 |

4. Prioritize Gaps

Rank uncovered areas by business impact:

Critical — auth, payment, core features → test first
High — user-facing CRUD, search, navigation
Medium — settings, preferences, edge cases
Low — static pages, about, terms

5. Suggest Test Plan

For each gap, recommend:

Number of tests needed
Which template from templates/ to use
Estimated effort (quick/medium/complex)

## 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

6. Auto-Generate (Optional)

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.

Output

Coverage matrix (table format)
Coverage percentage estimate
Prioritized gap list with effort estimates
Option to auto-generate missing tests

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most test skills give in 634 tokens

Counted across 964 of the 1,571 authors here whose files we hold, read 2026-08-07

Close the browser when donein 55 of 964, across 12 files
Wait for network idle statein 51 of 964, across 6 files
Launch Chromium in headless modein 49 of 964, across 6 files
Use descriptive selectors for elementsin 49 of 964, across 6 files
Run provided scripts with help flag firstin 49 of 964, across 6 files
Add appropriate explicit waitsin 48 of 964, across 5 files
Use bundled scripts as black boxesin 46 of 964, across 3 files
Do not read script source codein 46 of 964, across 3 files
Use sync playwright for scriptsin 46 of 964, across 3 files
Inspect dom before executing actionsin 46 of 964, across 3 files
Run the full test suitein 37 of 964
Write the failing test firstin 29 of 964, across 23 files

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.