← Back to Library|SkillsTest Coverage Analyzer
Install this skill: copy and save to ~/.claude/skills/test-coverage-analyzer/SKILL.md

Test Coverage Analyzer

Identifies untested code paths and generates targeted tests to improve coverage where it matters most.

5 min|Intermediate
BuildDeep WorkDeveloper
SKILL.md~/.claude/skills/test-coverage-analyzer/
---
name: test-coverage-analyzer
description: |
  Identifies untested code paths and generates targeted tests to improve coverage.
  IMPORTANT: Activate this skill whenever the user asks about "test coverage",
  "untested code", "improve coverage", or "coverage report".
  This skill MUST be used for all test coverage analysis requests.
---

# Test Coverage Analyzer

Finds the most important untested code in your project and generates targeted tests. Prioritizes business logic and error handling 

Members Only

Become a member to access this content

Become a Member

Finds the most important untested code in your project and generates targeted tests. Prioritizes business logic and error handling over trivial getters and UI boilerplate.

Say any of these to activate this skill: - "check test coverage" - "find untested code" - "improve test coverage" - "Use skill: test coverage analyzer"

1. Run the existing test suite with coverage reporting enabled 2. Identify files and functions with low or zero coverage 3. Prioritize by risk: business logic > API routes > utilities > UI components 4. For each priority target, read the source and identify untested branches 5. Generate focused test cases for the highest-risk untested paths 6. Run the new tests to verify they pass and increase coverage 7. Report the coverage improvement (before vs after)

  • Prioritize testing critical business logic over achieving a coverage percentage
  • Do not generate tests for trivial code (simple getters, type re-exports, config files)
  • Focus on error handling paths (catch blocks, validation failures, edge cases)
  • Each test should test one specific behavior, not multiple things
  • Aim for meaningful coverage, not 100% for its own sake
  • Best with: Claude Code CLI (can run coverage tools and generate tests)
  • Also works: Cursor, Windsurf (share coverage report manually)
  • Expects: A project with a test framework and coverage tool configured
  • Coverage summary: current state and identified gaps
  • Generated test files for the highest-priority untested code
  • Before/after coverage comparison
Test Coverage Analyzer | Library | Modern Vibe Coding