verification-before-completion

To prevent premature task completion claims, enforce a strict verification process that demands fresh evidence from tests, linters, and builds before reporting success. This ensures honesty and accuracy by requiring concrete proof of verification at all stages from coding to deployment.

Evidence-based verification in software engineering is the practice of running critical commands like tests and linters, then actively reviewing their output and exit codes before stating work is complete. It prevents shipping incomplete or buggy work due to rushed judgments or rationalizations.

Verify code review requirements before claiming success by running your test suite and build commands, then checking for a zero exit code. This process identifies and blocks common red flag behaviors, ensuring you actively check the output rather than assuming the work is functional.

Your build may pass but tests fail before deployment when verification steps are skipped or assumed successful. You must run the test suite, verify all tests pass with a zero exit code, and review the actual output to prevent shipping incomplete work due to common rationalizations.

Yes, you need to run linters and tests for every code change before completion. Mandatory verification requires running critical commands and reviewing their output to ensure requirement fulfillment, preventing the premature declaration of task success across all stages of work.

The best way to enforce quality assurance checks before task completion is establishing a mandatory verification process that requires fresh evidence from tests and builds. This combats rushed judgments by demanding concrete proof of verification and identifying common failure points.