vcp-coverage-gaps

Map source files to tests and identify untested functions with priority levels.

14|3|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/Z-M-Huang/vcp --skill vcp-coverage-gaps
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vcp-coverage-gaps
Source: https://github.com/Z-M-Huang/vcp/tree/main/plugins/vcp/skills/vcp-coverage-gaps
Command: npx skills add https://github.com/Z-M-Huang/vcp --skill vcp-coverage-gaps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify untested or under-tested code by mapping source files to tests, helping teams surface coverage gaps before they become defects.

Core Features & Use Cases

  • Coverage mapping: correlate source files with likely test counterparts to surface missing tests.
  • Public-API awareness: enumerate exported functions and assess test coverage across modules.
  • Prioritized remediation: categorize gaps by risk and impact to guide testing focus.

Quick Start

Run the skill on a codebase to generate a prioritized coverage gaps report.

Frequently Asked Questions about vcp-coverage-gaps

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

FAQPage Schema
How do I identify untested code and coverage gaps in a multi-language project?

Coverage gap analysis works by reading source files to enumerate exported public functions and mapping them to likely test counterparts. It categorizes missing tests by priority levels to guide remediation and surface untested code before defects occur.

How do I find missing tests for public functions in my codebase?

Finding missing tests involves mapping source files to test suites and assessing public-API awareness across modules. The skill enumerates exported functions, checks for corresponding tests, and highlights untested code gaps with priority levels for remediation.

Does this coverage gap analysis tool work with multi-language test suites?

Yes, this coverage gap analysis applies to multi-language projects with test suites and typical naming conventions. It correlates source files with likely test counterparts to surface missing tests across different programming languages.

What is the best way to prioritize test coverage remediation for untested modules?

The best way to prioritize test coverage remediation is to categorize untested code gaps by risk and impact. This skill generates a prioritized coverage gaps report that guides testing focus toward high-risk public functions lacking corresponding tests.

Can I map source files to test counterparts without configuring external dependencies?

Yes, you can map source files to test counterparts without external dependencies. The skill reads source files directly to enumerate public functions and checks for corresponding tests using typical naming conventions to highlight coverage gaps.