Test Coverage Analysis

Identify untested code paths and generate test specifications with a JSON report.

Updated Mar 3, 2026
One-click install
npx skills add https://github.com/StrategicMilk/Vetinari-Orchestrastor --skill test-coverage-analysis-strategicmilk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Test Coverage Analysis
Source: https://github.com/StrategicMilk/Vetinari-Orchestrastor/tree/main/vetinari/skills/catalog/inspector/test-coverage-analysis
Command: npx skills add https://github.com/StrategicMilk/Vetinari-Orchestrastor --skill test-coverage-analysis-strategicmilk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifies untested code paths, prioritizes high‑risk gaps, and automatically creates detailed test specifications to improve coverage.

Core Features & Use Cases

  • Coverage Data Collection: Gathers line, branch, and function coverage from existing test runs.
  • Gap Identification & Prioritization: Detects missing tests, ranks them by risk, and evaluates semantic coverage.
  • Test Specification Generation: Produces ready‑to‑implement test cases with inputs, expected outcomes, and mocking details.
  • Reporting & Estimates: Outputs a JSON report with metrics, projected coverage improvements, effort estimates, and quality issue analysis.
  • Use Case: Run after a new feature merge or before a release to ensure critical paths are thoroughly tested.

Quick Start

Ask the inspector to analyze test coverage for the file vetinari/planning/decomposition.py using the current codebase.

Frequently Asked Questions about Test Coverage Analysis

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

FAQPage Schema
How do I find untested code paths and improve test coverage?

To improve test coverage, you can analyze source code modules to identify untested code paths, prioritize high-risk gaps, and generate ready-to-implement test specifications with expected inputs and outcomes.

What's the best way to auto-generate missing tests during a code review?

Auto-generating missing tests during code review involves analyzing the source module to detect coverage gaps, then producing structured test specifications that include required mocking details and expected outcomes for immediate implementation.

Can I use test coverage analysis for pre-release quality checks?

Yes, test coverage analysis supports pre-release quality checks by evaluating line, branch, and function coverage to detect missing tests and outputting a JSON report with projected coverage improvements and effort estimates.

How does semantic test coverage gap prioritization work?

Semantic test coverage gap prioritization works by evaluating existing test runs to detect missing tests, ranking those gaps by risk level, and generating prioritized test specifications to target the most critical untested code paths first.

What do I need to generate test specifications from existing code?

To generate test specifications from existing code, you need the source code modules and existing coverage data from test runs, which are analyzed to produce ready-to-implement test cases with inputs, expected outcomes, and mocking details.