coverage-mapper

What problem does it solve?

This Skill eliminates the guesswork of test prioritization and test-to-source mapping, so you don't waste time writing tests for low-risk code while critical paths like authentication, payments, and security logic remain untested.

Core Features & Use Cases

• Bidirectional file-test mapping: Builds and maintains maps of which tests cover which source files, enabling smart test selection to run only relevant tests for changed code and speed up CI pipelines.
• Risk-ranked uncovered code inventory: Maps every uncovered code region to a risk score weighted by module criticality, code churn, cyclomatic complexity, and PR delta, so you know exactly where to add tests first instead of chasing overall coverage percentages.
• Intelligent categorization: Automatically suppresses trivial uncovered code (getters, DTO fields, dead code with no callers) and surfaces high-risk gaps like untested error paths, security conditionals, and new PR code with no coverage to reduce noise for test writers.
• Use Case: For a PR that adds new payment processing logic, the mapper flags untested error paths in the payment module as critical risk, lists existing tests that cover related code for fast validation, and suggests exact test cases to cover the gaps.

Quick Start

Use the coverage-mapper skill to generate a risk-ranked map of uncovered code regions for your current project, highlighting high-risk gaps in your open pull request and suggesting exactly where to add tests next.