test-coverage-analyzer

Analyze test coverage and prioritize missing tests by risk.

2|Updated Mar 19, 2026

Search Tags:#vitest #quality assurance #unit testing #test generation #jest #test coverage #test prioritization

Ready to run

npx skills add https://github.com/EvanPluchart/kyomu --skill test-coverage-analyzer-evanpluchart

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test-coverage-analyzer
Source: https://github.com/EvanPluchart/kyomu/tree/main/.claude/skills/test-coverage-analyzer
Command: npx skills add https://github.com/EvanPluchart/kyomu --skill test-coverage-analyzer-evanpluchart

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams understand test coverage, identify the highest-risk untested areas, and focus on writing the most valuable tests to reduce regression and security risk.

Core Features & Use Cases

Detects the test framework: Automatically identifies whether the project uses Jest or Vitest (and other common harnesses via configuration files).
Analyzes and maps coverage: Either parses coverage reports when available or infers coverage gaps by correlating source files with existing test files.
Prioritizes by risk and impact: Scores uncovered files using domain criticality, complexity, and dependency impact, then produces an ordered test plan.
Generates test suggestions and code guidance: In generate mode, creates targeted test files using project-specific testing patterns (evan-workflow conventions).

Quick Start

Run the skill in analyze mode to produce a coverage map and an ordered list of critical files that should receive tests first.

Frequently Asked Questions about test-coverage-analyzer

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

FAQPage Schema

How do I identify the highest-risk untested areas in my codebase?▼

You can prioritize missing tests by scoring uncovered files using domain criticality, complexity, and dependency impact. This approach helps focus on writing the most valuable tests to reduce regression and security risk before releases or after major refactors.

Does this test coverage analyzer work with Jest and Vitest?▼

Yes, the analyzer automatically detects whether your project uses Jest, Vitest, or other common harnesses via configuration files. It then parses existing coverage reports or infers gaps by correlating source files with test files.

What is the best way to generate unit tests for critical business logic?▼

The best way to generate unit tests for critical logic is to use an analyzer that scores uncovered areas by risk and optionally scaffolds targeted test files following project-specific naming and structure patterns.

How do I map test coverage across different domains like API endpoints and validators?▼

To map test coverage across domains like API endpoints and validators, run the analyzer in analyze mode. It produces a global and per-domain coverage map to pinpoint uneven coverage and highlight critical files needing tests.

When should I prioritize test gaps in my repository?▼

You should prioritize test gaps during ongoing development before releases, after major refactors, or whenever coverage is suspected to be uneven across domains like auth, core business logic, API endpoints, validators, UI, and utilities.