coverage-check

Code coverage thresholds are enforced by analyzing current snapshots against configured global and module-specific limits to flag gaps in critical files and output a structured summary. It provides an optional delta comparison for pull requests to guide merge decisions.

Checking critical file code coverage involves loading thresholds from coverage-config.json and pruning gaps in critical areas. The process identifies gaps in critical areas, correlates them with global metrics, and flags them for actionable remediation.

Module-specific code coverage checks can be applied across a project by loading configured module thresholds. The system correlates these module metrics with global metrics to ensure comprehensive quality gate enforcement and reduce regression risk.

A code coverage delta report for PR reviews is generated by comparing current snapshots against baselines. This delta comparison identifies coverage variations to guide merge decisions and outputs a structured diagnosis file named coverage-check-result.yaml.

Automating code coverage gates in a CI-CD pipeline ensures minimum coverage across a project is enforced consistently. This automation reduces regression risk and ensures quality gates pass before code merges.

Coverage-check works without additional dependencies to validate the latest snapshot against configured thresholds. You run the /coverage-check command to analyze reports, enforce limits, and generate a history of gaps.