test-coverage

Analyze test coverage and identify gaps with recommended tests.

1|Updated Jul 25, 2025
One-click install
npx skills add https://github.com/masta-g3/rules --skill test-coverage-masta-g3
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-coverage
Source: https://github.com/masta-g3/rules/tree/main/skills/test-coverage
Command: npx skills add https://github.com/masta-g3/rules --skill test-coverage-masta-g3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Assessing test coverage manually is time-consuming and error-prone; this Skill helps teams quickly evaluate coverage, identify gaps, and prioritize tests to improve quality.

Core Features & Use Cases

  • Survey infrastructure: Determine the testing framework, locate tests, and understand execution commands.
  • Map critical paths: Identify data integrity, authentication, business logic, integration points, and error handling with risk impact.
  • Identify gaps: Classify coverage as covered, partial, or gap to prioritize remediation.
  • Report to user: Produce a concise summary with recommended tests and actionable next steps.

Quick Start

Provide the project context and test suite so I can assess coverage, identify gaps, and propose essential tests.

Frequently Asked Questions about test-coverage

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

FAQPage Schema
How do I identify test coverage gaps in my project's test suite?▼

Generating a test coverage report involves mapping critical paths such as business logic and integration points, identifying coverage gaps, and returning a concrete report detailing risk exposure and recommended tests.

What is the best way to prioritize test improvements for critical paths?▼

The best way to prioritize test improvements is to classify coverage status across critical paths and error handling, determining risk impact to produce a concise summary with actionable next steps.

Can I assess test coverage for error handling and data flow without specific testing framework dependencies?▼

Yes, assessing test coverage works without specific dependencies by surveying the existing project infrastructure to locate tests, map data flow, and identify gaps in error handling and business logic.

How do I evaluate risk exposure for uncovered business logic and integration points?▼

Evaluate risk exposure by mapping critical paths including business logic and integration points, classifying coverage status to identify gaps, and detailing risk impact in a comprehensive coverage report.