verification-before-completion

To prevent false positives during code completion, you must enforce an evidence-based verification protocol that mandates running specific commands and checking their outputs before asserting any task success.

The best way to verify tests before a code commit is to independently execute the test suite and confirm the output explicitly shows zero failures, preventing rationalization and ensuring actual quality assurance.

Yes, the verification process applies to all stages of development and deployment, including code commits, pull requests, and agent task finalization, wherever success is asserted.

You enforce quality assurance before deployment by applying a strict gate function that requires confirming all acceptance criteria are met through defined checks and command outputs before finalizing.

You should never skip verification steps when rationalizing task completion, as doing so risks costly errors and false positives; the protocol provides clear counter-arguments against common excuses for skipping these checks.