verification-before-completion

To prevent premature code completion claims, enforce an evidence-before-assertions policy by running specific verification commands and reviewing their output before stating any work is complete.

Mandatory verification before claiming a bug fix is successful requires running the relevant test command, checking its output for success, and only then confirming the fix is complete and honest.

Shipping incomplete features happens due to premature success declarations; quality assurance catches it by identifying red flags and rationalizations, enforcing strict verification reviews before completion assertions.

To verify a build succeeds before declaring work status, run the specific build command, review the output to confirm success, and avoid making any positive status claims until the evidence is checked.

Yes, you need to run tests before claiming code review is complete because an evidence-based verification policy mandates checking test outputs to ensure honesty and prevent unverified fixes.

Common rationalizations for skipping verification include assuming previous success guarantees current results, but strict quality assurance requires reviewing command outputs to prevent dishonest completion claims.