check-coverage

To enforce a minimum pytest coverage threshold, the Skill automates test-coverage evaluation and gap remediation, failing the build until the defined percentage target is met. It prioritizes fixes on critical paths to ensure code health during CI/CD pipelines or local development.

The best way to fix test coverage gaps is to run automated coverage checks that analyze the report and prioritize tests improving coverage on critical paths. The Skill guides fixes by detecting shortfalls and validating improvements until the target threshold is reached.

Yes, you need pytest, pytest-cov, and a Makefile target such as make test-cov-check to reproduce and validate improvements. These dependencies are required for the Skill to measure coverage, identify gaps, and enforce the minimum threshold locally or in CI.

Automated test coverage evaluation works by running tests, analyzing the coverage report, and detecting shortfalls to guide fixes. During refactors or feature updates, it prioritizes tests that improve coverage on critical paths and enforces a minimum threshold to maintain code health.

Yes, you can use this to enforce quality assurance thresholds for new contributors by setting a minimum coverage percentage like 80%. The Skill automates test-coverage evaluation and gap remediation, ensuring code health during onboarding by re-running tests until the target is met.

Your test coverage check may fail to detect gaps if the minimum threshold is not properly configured or the Makefile target is missing. The Skill requires pytest and pytest-cov to analyze the report, prioritize critical path fixes, and validate improvements until the target is met.