test-coverage

Parse coverage reports and generate test scaffolds for untested code areas.

11|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/berkcangumusisik/claude-code-practices --skill test-coverage-berkcangumusisik
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-coverage
Source: https://github.com/berkcangumusisik/claude-code-practices/tree/main/skills/test-coverage
Command: npx skills add https://github.com/berkcangumusisik/claude-code-practices --skill test-coverage-berkcangumusisik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Uncovered code in projects leads to flaky behavior and hidden defects. This Skill automatically analyzes coverage reports to locate untested files and generates missing tests to raise overall code quality.

Core Features & Use Cases

  • Analyze coverage reports across supported runtimes to identify files with low coverage.
  • Propose and generate tests for the most under-tested files to close coverage gaps.
  • Produce a concise test coverage report highlighting changes and expected improvements.

Quick Start

Analyze your project's coverage data and generate tests for untested areas in the most under-tested files.

Frequently Asked Questions about test-coverage

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

FAQPage Schema
How do I generate tests for untested code areas from a coverage report?

Yes, you can use this Skill with pytest. It parses standard coverage report outputs from supported runtimes like pytest, nyc, and go test to identify untested files and generate automated test scaffolds for them.

How do I find code coverage gaps in my project automatically?

This Skill focuses strictly on the top three under-tested files identified in your coverage reports to generate test scaffolds, limiting scope to raise overall code quality rather than covering the entire project at once.

Does this work with nyc and go test coverage outputs?

Yes, this Skill works with nyc and go test. It parses coverage outputs from these runtimes to identify files with low coverage and proposes missing tests for the untested cases.

What is the best way to turn coverage gaps into automated tests?

The best way to turn coverage gaps into automated tests is to parse coverage outputs, read the corresponding source files, and generate test scaffolds for the untested cases in the most under-tested files.

Why does this Skill only generate tests for some files and not the whole project?

This Skill only generates tests for some files to focus on the top three under-tested files identified in the coverage reports, ensuring targeted improvements to close the most critical coverage gaps first.