long-task-quality

You can enforce code coverage and mutation testing thresholds by running this Skill to execute predefined scripts that validate test outputs against project-specific requirements, ensuring concrete quality evidence before marking a feature complete.

Automated quality gates are sequential validation checks for test verification, code coverage, and mutation testing scores that prevent software features from being marked as complete without fresh, verifiable evidence of quality.

Yes, you can use this quality gate process after a TDD cycle to automatically run all tests, validate if coverage meets the 90% line and 80% branch threshold, and ensure the mutation score is above 80%.

Yes, the mutation testing verification works without external dependencies by executing predefined scripts and references to validate outputs against project-specific requirements for evidence-based completion.

The best way to prevent poorly tested code from being merged is to implement a multi-stage quality gate process that requires passing real test verification, coverage thresholds, and mutation testing scores before completion.