coverage-analyzer

Analyze JavaScript/TypeScript test coverage reports to identify untested files and prioritize improvements.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/physics91/claude-vibe --skill coverage-analyzer-physics91
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coverage-analyzer
Source: https://github.com/physics91/claude-vibe/tree/main/skills/coverage-analyzer
Command: npx skills add https://github.com/physics91/claude-vibe --skill coverage-analyzer-physics91

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill analyzes test coverage, identifies untested files, and prioritizes coverage improvements to raise quality and confidence.

Core Features & Use Cases

  • Untested files detection: lists high-priority areas needing tests.
  • Coverage metrics: tracks lines, branches, and function coverage against targets.
  • Improvement roadmap: offers 1-3 prioritized changes to raise coverage.
  • Use Case: Focus test effort on critical business logic with highest uncovered risk.

Quick Start

Run the coverage-analyzer on your project to see current coverage and recommended actions.

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 files in my JavaScript project?

Coverage-analyzer scans your JavaScript/TypeScript project to detect untested files and low-coverage regions. It ingests coverage reports (like Jest LCOV output) and outputs a prioritized list of files needing test attention, helping you focus test effort on critical gaps.

Can I use coverage analysis to prioritize which tests to write first?

Yes. The Skill analyzes coverage metrics across lines, branches, and functions, then generates a prioritized roadmap with 1-3 recommended improvements. It ranks untested areas by business logic risk so you write tests for the highest-impact gaps first.

What coverage formats does this tool accept?

Coverage-analyzer processes LCOV coverage reports, commonly generated by Jest and other JavaScript/TypeScript test runners. It accepts coverage data, file patterns, and exclusion lists to filter results and output structured metrics with actionable recommendations.

How do I track coverage improvements over time?

The Skill outputs structured coverage metrics (lines, branches, functions) against defined targets. You run it on successive coverage reports to compare metrics and measure progress, letting you validate whether test improvements are raising overall coverage.

Does coverage analysis work with monorepos or multiple test suites?

Coverage-analyzer accepts file patterns and exclusion lists as input, enabling you to filter results by directory, module, or suite. This lets you analyze coverage selectively across monorepo packages or focus on specific test suites within a larger project.