test-coverage

Run automated test coverage analysis and report uncovered classes, branches, and lines.

2|1|Updated Nov 7, 2025
One-click install
npx skills add https://github.com/is-ivanov/rpm-ddd --skill test-coverage-is-ivanov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-coverage
Source: https://github.com/is-ivanov/rpm-ddd/tree/main/.opencode/skills/test-coverage
Command: npx skills add https://github.com/is-ivanov/rpm-ddd --skill test-coverage-is-ivanov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you verify whether recent or existing code is adequately tested by running coverage analysis and surfacing the exact classes, branches, and lines that remain untested.

Core Features & Use Cases

  • Coverage execution and reporting: Runs tests with coverage for a selected module and stops early if tests fail.
  • Gap analysis: Identifies uncovered classes, extracts uncovered lines from reports, and reads source code to show the real missing logic.
  • Focused validation after changes: Supports filtering by class name or restricting analysis to recently changed files so you can confirm new work is properly covered after a green phase.
  • Use case: After implementing a new use case or REST controller, use this Skill to check whether the changed code paths are fully exercised and to pinpoint the scenarios still missing tests.

Quick Start

Ask the AI to run the test-coverage skill for a target module such as usecase or rest and optionally focus only on recently changed classes.

Frequently Asked Questions about test-coverage

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

FAQPage Schema
How do I find untested code in my backend module after recent commits?

To find untested code, run automated test coverage analysis filtered by recently changed files. This validates new work after a green phase and surfaces exact classes, branches, and source lines missing tests.

What is the best way to identify uncovered branches and lines in a specific class?

Identifying uncovered branches is done by running test coverage analysis restricted to a specific class name. The process parses coverage reports and reads source code to show the real missing logic.

How does parsing JaCoCo CSV and XML reports help with test gap analysis?

Parsing JaCoCo CSV and XML reports extracts uncovered lines and classifies reachable gaps for remediation. This test gap analysis reveals whether code paths are fully exercised by existing tests.

Can I run coverage analysis on a single module like usecase or rest without executing the entire test suite?

Yes, you can execute test coverage for a selected module such as usecase or rest. The analysis stops early if tests fail, ensuring module-level validation without completing a broken suite.

What happens to my test coverage analysis if the test suite fails during execution?

If the test suite fails during execution, the test coverage analysis stops early. This prevents parsing incomplete reports and ensures you only analyze gaps when tests pass successfully.