Analyze Test Coverage Gaps
Analyzes test coverage gaps by mapping the application's testable surfaces (routes, components, APIs, user flows) against existing tests, producing a coverage matrix, prioritized gap list, and recommended test plan.
✨ What it does
- Maps application routes, components, API endpoints, and user flows.
- Scans existing test files to determine coverage.
- Generates a coverage matrix with status indicators.
- Prioritizes gaps by business impact (critical, high, medium, low).
- Suggests a test plan with number of tests, templates, and effort estimates.
- Optionally auto-generates tests for selected gaps.
🎯 When to use it
- When the user asks about test coverage or what's not tested.
- When the user wants to identify missing tests before a release.
- When the user needs a prioritized list of areas to add tests.
- When the user wants to generate tests for uncovered areas.
🚀 How to use
Trigger: /register
Trigger by asking about test coverage, e.g., 'test coverage', 'what's not tested', 'coverage gaps', 'missing tests', 'coverage report', or 'what needs testing'. The skill expects access to the application's route definitions, component files, API routes, and existing test files. Example prompts:
What are the test coverage gaps in this project?
Generate a coverage report and suggest tests for missing areas.
📄 Output: A coverage matrix, coverage percentage estimate, prioritized gap list with effort estimates, and an optional test plan.
📦 Add this skill to Claude Code
# 1. Get the skills repo
git clone --depth 1 https://github.com/alirezarezvani/claude-skills /tmp/claude-skills
# 2. Copy this skill into your project (or ~/.claude/skills for all projects)
mkdir -p .claude/skills
cp -r /tmp/claude-skills/engineering-team/playwright-pro/skills/coverage .claude/skills/coverageSkill source: engineering-team/playwright-pro/skills/coverage/SKILL.md
⚠️ Good to know
Requires the application to be accessible for scanning and existing test files to be present; the skill does not run tests but analyzes static code.
❓ FAQ
How does the skill determine coverage?
It maps the application surface (routes, components, APIs) and scans existing test files to see which areas are referenced by page.goto() calls, locators, or API mocks.
Can it automatically generate tests for gaps?
Yes, after presenting the prioritized gaps, it asks if you want to generate tests for the top gaps and can invoke the /pw:generate command with recommended templates.
What output does it produce?
It produces a coverage matrix table, a coverage percentage estimate, a prioritized list of gaps with effort estimates, and optionally a test plan.
🤖 Overview, features, install steps and FAQ were generated from the project's SKILL.md on Sep 4, 2026. Always check the original source before running commands.