coverage-analyzer

Compare source files with tests to identify untested code coverage gaps.

1|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/tanujsutaria/VitalArc --skill coverage-analyzer-tanujsutaria
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coverage-analyzer
Source: https://github.com/tanujsutaria/VitalArc/tree/main/.claude/skills/coverage-analyzer
Command: npx skills add https://github.com/tanujsutaria/VitalArc --skill coverage-analyzer-tanujsutaria

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify untested code by analyzing source files and their corresponding tests to surface coverage gaps.

Core Features & Use Cases

  • Surface coverage gaps across domains (Domain/UseCases, Entities, Presentation, Infrastructure) and rank files by impact.
  • Generate a concise priority report that guides test efforts and optimizes CI workflows.
  • Use in pull requests to quickly identify high-risk untested areas and track test progress over time.

Quick Start

Run the Coverage Analyzer on the current repository with default settings to produce a prioritized test-gap report.

Frequently Asked Questions about coverage-analyzer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify untested code in my source files?

To identify untested code, compare your source files with their corresponding tests to surface coverage gaps. The analyzer scans multiple layers like domain, presentation, and infrastructure to reveal exactly where tests are missing.

How do I prioritize test goals for untested source files?

Prioritize test goals by ranking untested source files based on their impact. The analyzer generates a concise priority report that guides your test efforts toward high-risk areas and optimizes CI workflows.

Can I use a coverage analyzer in CI pipelines?

Yes, you can use this coverage analyzer in CI pipelines or local development. It operates across multiple architectural layers to guide where tests are most needed and helps track test progress over time.

Does the tool surface coverage gaps across domain and presentation layers?

Yes, the tool surfaces coverage gaps across domain, presentation, and infrastructure layers. It matches source files with their tests and highlights untested areas within these specific architectural boundaries.

What is the best way to track test progress over time in pull requests?

Track test progress over time by running the analyzer in pull requests to quickly identify high-risk untested areas. It generates an action-oriented report that highlights remaining coverage gaps and guides new test efforts.