validate-coverage-threshold

Test coverage validation checks if your codebase meets predefined coverage targets (e.g., 80% overall, 75% branches) by parsing coverage reports. It automatically flags insufficient coverage in CI/CD pipelines, quality gates, or pre-commit checks, identifying specific files below thresholds and blocking progression when targets aren't met.

The Skill extracts overall, statement, branch, and function coverage percentages from coverage/coverage-summary.json or test output. It compares each metric against configurable thresholds and outputs structured results showing coverage values, threshold targets, pass/fail status, and uncovered files for prioritized testing.

Yes, this Skill is designed for JavaScript/TypeScript projects using standard coverage report formats. It reads from coverage/coverage-summary.json or test output files, making it compatible with common coverage tools in these ecosystems integrated into CI/CD pipelines and QA workflows.

The Skill accepts configurable minimum thresholds for overall coverage, statements, branches, and functions. Default values are 80% overall, 80% statements, 75% branches, and 80% functions. You customize these targets to match your project's quality standards before validation runs.

When coverage metrics fail to meet thresholds, the Skill outputs a failure status with the list of uncovered files and specific metrics that didn't pass. The canProceed flag is set to false, preventing pipeline progression and prompting developers to add tests for flagged components.

Coverage validation works in multiple contexts including CI/CD gates, pre-commit checks, and QA pipelines. It parses local coverage data and returns structured results compatible with hook systems, allowing you to block commits when coverage targets aren't met before code reaches the repository.