coverage

Aggregate coverage reports across languages to identify untested code paths.

39|6|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/mayurpise/draft --skill coverage-mayurpise
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coverage
Source: https://github.com/mayurpise/draft/tree/main/skills/coverage
Command: npx skills add https://github.com/mayurpise/draft --skill coverage-mayurpise

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams understand and improve test coverage by aggregating results from coverage reports and highlighting untested code paths.

Core Features & Use Cases

  • Unified Coverage View: Gather coverage data from popular tools (nyc, pytest-cov) and present a single, actionable report.
  • Gap Detection: Automatically identify uncovered lines and branches with suggested test actions.
  • CI & Workflows: Integrate coverage insights into CI dashboards to track trends and quality over time.

Quick Start

Run an initial coverage analysis using your project’s test runner and review the resulting report to identify and remediate gaps.

Frequently Asked Questions about coverage

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

FAQPage Schema
How do I identify test coverage gaps in a multi-language project?

To identify test coverage gaps in a multi-language project, you aggregate coverage reports from standard tools like nyc and pytest-cov. This process highlights untested code paths and branches, enabling developers to prioritize and fix uncovered code.

How does test coverage aggregation work for CI pipelines?

Test coverage aggregation for CI pipelines works by gathering coverage data from standard tools like nyc and pytest-cov. It presents a unified report that integrates into CI dashboards to track quality trends over time.

Can I use pytest-cov and nyc reports together to find untested code paths?

Yes, you can use pytest-cov and nyc reports together to find untested code paths. The aggregation process gathers data from both tools to automatically identify uncovered lines and branches with suggested test actions.

Do I need access to my repository's test commands to generate actionable coverage results?

Yes, you need access to your repository's test commands to generate actionable coverage results. Running an initial coverage analysis using your project's test runner is required to review the resulting report and remediate gaps.

What's the best way to track code quality and coverage trends over time?

The best way to track code quality and coverage trends over time is by integrating coverage insights into CI dashboards. This allows teams to monitor unified coverage data and identify untested paths across multi-language projects continuously.