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".
Best use case
coverage is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Analyze test coverage gaps. Use when user says "test coverage", "what's not tested", "coverage gaps", "missing tests", "coverage report", or "what needs testing".
Teams using coverage should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/coverage/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How coverage Compares
| Feature / Agent | coverage | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this 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".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
SKILL.md Source
# 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 2. **High** — user-facing CRUD, search, navigation 3. **Medium** — settings, preferences, edge cases 4. **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
Related Skills
wiki-query
Query the LLM Wiki — reads index.md first, drills into 3-10 relevant pages, synthesizes an answer with inline [[wikilink]] citations, and offers to file the answer back as a new comparison or synthesis page. Usage /wiki-query "<question>"
wiki-log
Show recent entries from the LLM Wiki log (wiki/log.md). Uses the standardized
wiki-lint
Run a health check on the LLM Wiki vault — mechanical checks (orphans, broken links, stale pages, missing frontmatter, log gap, duplicates) plus semantic checks (contradictions, cross-reference gaps, concepts missing their own page). Outputs a markdown report with suggested actions. Usage /wiki-lint [--stale-days N] [--log-gap-days N]
wiki-init
Bootstrap a fresh LLM Wiki vault with the three-layer structure, schema files, and starter templates. Usage /wiki-init <path> --topic "<topic>" [--tool all|claude-code|codex|cursor|antigravity]
wiki-ingest
Ingest a source file from raw/ into the LLM Wiki — read, discuss, write summary page, update cross-references across 5-15 pages, regenerate index, append to log. Usage /wiki-ingest <path-to-source>
tc
Track technical changes with structured records, a state machine, and session handoff. Usage: /tc <init|create|update|status|resume|close|export|dashboard> [args]
tc-tracker
Use when the user asks to track technical changes, create change records, manage TC lifecycles, or hand off work between AI sessions. Covers init/create/update/status/resume/close/export workflows for structured code change documentation.
llm-wiki
Use when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
karpathy-coder
Use when writing, reviewing, or committing code to enforce Karpathy's 4 coding principles — surface assumptions before coding, keep it simple, make surgical changes, define verifiable goals. Triggers on "review my diff", "check complexity", "am I overcomplicating this", "karpathy check", "before I commit", or any code quality concern where the LLM might be overcoding.
karpathy-check
Run Karpathy's 4-principle review on staged changes or the last commit. Checks complexity, diff noise, hidden assumptions, and goal verification. Usage /karpathy-check [--last-commit]
cs-wiki-linter
Dispatched sub-agent that runs a periodic health check on an LLM Wiki vault. Runs mechanical checks via scripts (orphans, broken links, stale pages, missing frontmatter, duplicate titles, log gaps), does semantic checks (contradictions, stale claims, cross-reference gaps, concepts missing their own page), and produces a markdown report with suggested actions. Spawn weekly, after batch ingests, or when the user says "check the wiki" / "lint my wiki" / "audit the vault".
cs-wiki-librarian
Dispatched sub-agent that answers queries against an LLM Wiki vault. Reads index.md first, drills into 3-10 relevant pages across categories, synthesizes an answer with inline [[wikilink]] citations, and offers to file the answer back into the wiki as a new comparison or synthesis page. Spawn when the user asks a substantive question the wiki might answer, says "what does the wiki say about X", "compare A and B across my sources", or wants to explore a topic.