Map source files to covering tests and rank uncovered code by risk.
npx skills add https://github.com/robotijn/ctoc --skill coverage-mapper
Please help me install this Agent Skill. Skill: coverage-mapper Source: https://github.com/robotijn/ctoc/tree/main/skills/testing/coverage-mapper Command: npx skills add https://github.com/robotijn/ctoc --skill coverage-mapper
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.
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.
High-intent search queries and answers about installing and using this skill.
Risk-ranked uncovered code inventory maps every untested region to a risk score weighted by module criticality, code churn, cyclomatic complexity, and PR delta. This identifies high-risk gaps like untested security conditionals so you target test efforts to critical paths instead of chasing vanity coverage metrics.
Bidirectional file-test mapping builds and maintains relationships between source files and their covering tests. This enables smart test selection to run only relevant tests for changed code, speeding up CI/CD pipelines and pull request validation.
The coverage mapper delivers normalized JSON output compatible with Codecov, SonarQube, and custom refinement loops. This allows teams to import risk-weighted coverage data and uncovered code inventories directly into existing quality gates and reporting dashboards.
Intelligent categorization automatically suppresses trivial uncovered code including getters, DTO fields, and dead code with no callers. It surfaces high-risk gaps like untested error paths and new PR code with no coverage, reducing noise for test writers.
The coverage mapper analyzes PR diffs to flag untested error paths and new code with no coverage as critical risk. It lists existing tests covering related code for fast validation and suggests exact test cases to cover the gaps.
Risk-weighted coverage mapping suits legacy codebase modernization when teams need to target test efforts to high-risk paths rather than chasing overall coverage percentages. It applies to CI/CD pipelines and pull request reviews by prioritizing tests based on module criticality and code churn.
tientt010Calculate CRAP scores from cyclomatic complexity and test coverage for .NET projects.
ColdBoxGenerate HTML, Cobertura, and SonarQube XML coverage reports for ColdBox and BoxLang tests.
petrkohutGenerate end-to-end automated tests for existing software features.
EmilLindforsIdentify gaps in Rust test coverage and suggest missing test cases.
