verification-before-completion

To enforce verification before claiming code completion, apply a strict protocol requiring explicit evidence from executed commands, such as running test suites and confirming zero failures before stating work is done.

Common red flag phrases indicating a lack of testing verification include rationalizations that bypass running fresh commands, signaling premature assertions of success without concrete output evidence from executed tests.

Yes, you need to run test suites before stating bug fixes are complete to ensure honesty and accuracy in reporting work status, preventing premature assertions by backing claims with fresh command output.

Claiming a task is complete without evidence causes issues in software development because it leads to dishonest or premature work status reports, bypassing the necessary execution of verification commands to prove zero failures.

To verify passing tests before creating a pull request, run your test suite, confirm zero failures, and state "All tests pass" by providing the exact output count from the executed verification commands.