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".
Install
npx skills add adriannoes/awesome-agentic-ai --skill coveragegit clone --depth 1 https://github.com/adriannoes/awesome-agentic-ai.git /tmp/awesome-agentic-ai
mkdir -p ~/.claude/skills
cp -r /tmp/awesome-agentic-ai/cursor-claude-codex/skills/alirezarezvani-skills/playwright-pro/skills/coverage ~/.claude/skills/coveragePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# 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: 1. **Critical** — auth, payment, core features → test first
Details
- Skill name
coverage- Repository
- adriannoes/awesome-agentic-ai
- Path
cursor-claude-codex/skills/alirezarezvani-skills/playwright-pro/skills/coverage/SKILL.md- License
- MIT
- Repo updated
- 2 November 2026
- Copies
- Found in 4 GitHub repos
FAQ
What does the Coverage skill do?
Analyze test coverage gaps. Use when user says "test coverage", "what's not tested", "coverage gaps", "missing tests", "coverage report", or "what needs testing".
How do I install the Coverage skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add adriannoes/awesome-agentic-ai --skill coverage. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Coverage popular?
It lives in adriannoes/awesome-agentic-ai, which has 100 GitHub stars and 27 forks, and is included in 2 curated skill lists.
Related skills
Browserstack
100adriannoes/awesome-agentic-ai
Run tests on BrowserStack. Use when user mentions "browserstack", "cross-browser", "cloud testing", "browser matrix", "test on safari", "test on firefox", or "browser compatibility".
Fix
100adriannoes/awesome-agentic-ai
Fix failing or flaky Playwright tests. Use when user says "fix test", "flaky test", "test failing", "debug test", "test broken", "test passes sometimes", or "intermittent failure".
Generate
100adriannoes/awesome-agentic-ai
Generate Playwright tests. Use when user says "write tests", "generate tests", "add tests for", "test this component", "e2e test", "create test for", "test this page", or "test this feature".
Verify Work
292danielvm-git/bigpowers
Multi-phase UAT gate — cold-start smoke, build, typecheck, lint, tests, step-by-step manual verification, gaps-closure loop. Use after execute-plan or develop-tdd, before audit-code.
Init
100adriannoes/awesome-agentic-ai
Set up Playwright in a project. Use when user says "set up playwright", "add e2e tests", "configure playwright", "testing setup", "init playwright", or "add test infrastructure".
Validate Fix
292danielvm-git/bigpowers
Prove a fix works before declaring done — re-run the failing test, run the full suite, typecheck, lint, and harden against recurrence. Use after implementing a bug fix, when user says "is this fixed?", or before closing an investigation.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.