60-test-coverage

To enforce test coverage for changed TypeScript files, you need a workflow that identifies changed paths, measures baseline coverage, and blocks merges until the 80% threshold is met. This skill automates that exact phase-based enforcement process.

A CI workflow prevents regressions by measuring baseline coverage, recommending regression tests for uncovered changed lines, and re-linting until checks pass. This skill generates a final report comparing baseline versus final coverage for remediation.

Yes, this test coverage enforcement works with existing GitHub workflows and requires root-level npm scripts for test:coverage and lint:full to ensure end-to-end quality validation before merging code changes.

The best way to document required test coverage thresholds is through an automated phase-based workflow that reports uncovered changed lines for remediation. This skill provides baseline measurement, regression test recommendations, and final reporting.

Test coverage enforcement fails when lint checks are not green because strict quality assurance requires both testing and linting to pass. This skill ensures all changed code paths are tested and linted, running re-lint phases until validation succeeds.