verification-before-completion

To enforce automated testing and linting before merging code, this Skill runs a verification protocol encompassing unit tests, linters, and type checks. It ensures code quality by catching errors early and preventing regressions through a rigorous multi-step process.

A verification protocol for software quality assurance is a comprehensive process that runs automated checks, manual reviews, and integration validations. It ensures software quality by preventing incomplete or buggy code from being marked as complete.

To run a manual verification checklist before task completion, this Skill guides human review of functionality and user experience. It provides a structured protocol that complements automated testing to ensure complete feature validation.

Yes, you can use this verification process for CI/CD integration checks. It ensures changes haven't negatively impacted other system parts by running builds and tests, requiring adherence to a decision matrix for final sign-off.

The best way to prevent code regressions before completion is enforcing a multi-step verification protocol. This approach runs automated tests, linters, and build processes to catch errors early, blocking incomplete or buggy code from merging.