Parse cross-format coverage reports to enforce branch and diff thresholds and gate merges.
npx skills add https://github.com/robotijn/ctoc --skill coverage-enforcer
Please help me install this Agent Skill. Skill: coverage-enforcer Source: https://github.com/robotijn/ctoc/tree/main/skills/testing/coverage-enforcer Command: npx skills add https://github.com/robotijn/ctoc --skill coverage-enforcer
This Skill eliminates the risk of low-quality, incomplete test coverage (including line-only metrics, missing branch coverage, and assertion-free tests) slipping into production, which commonly leads to undetected bugs in high-stakes code paths like payment processing, authentication, and data validation.
Use the coverage-enforcer skill to analyze your project's latest coverage report, enforce branch and diff coverage thresholds for new code, and generate a merge approval or block decision with specific evidence for any uncovered critical paths.
High-intent search queries and answers about installing and using this skill.
Coverage enforcement blocks merges by parsing cross-format coverage reports like LCOV or Cobertura, validating branch and diff coverage thresholds, and generating a merge block decision with cited evidence for uncovered critical code paths.
Critical path testing validates essential code paths like payment processing by pairing coverage metrics with mutation testing, preventing assertion-free tests from passing merge gates by ensuring test assertions actually catch injected code mutations.
Yes, coverage enforcement supports legacy codebase audits by parsing over 10 coverage report formats including JaCoCo, Istanbul JSON, and Go coverage across major programming languages to identify coverage blind spots.
Yes, merge gating works for AI-generated code by applying multi-metric threshold enforcement to new diffs, ensuring AI-generated patches meet branch and critical-path coverage requirements before merging into production.
You should pair mutation testing with branch coverage because line coverage alone misses untested branches and assertion-free tests, while mutation testing validates that existing assertions actually fail when code is mutated, ensuring true test quality.
Diff coverage limitations vary by project type; greenfield projects require strict branch and critical-path enforcement across all code, while mature or legacy projects apply patch coverage thresholds to new changes to avoid blocking merges over historical blind spots.
mscipioParse LCOV, JSON, Clover XML, and Cobertura XML coverage reports.
liauw-mediaAutomate and enforce a pre-merge checklist for Pull Requests or Merge Requests.
Sheldon-92Execute test suites and report failures with coverage metrics.
eliottbusinessAutomate pre-commit code review with static analysis and security scanning.
