verification-before-completion

To prevent premature assertions during code completion, you must run specific verification commands and analyze their output for evidence before stating a task is complete or fixed.

Evidence-based verification for bug fixes is the process of running test suites, confirming zero failures in the output, and presenting this proof before making any success claims.

Enforce mandatory verification before committing code by establishing a strict process that mandates running test commands and confirming their output shows zero failures.

Claiming a task is fixed before running tests causes errors because unverified assertions bypass quality assurance, allowing failures to slip through without evidence of actual completion.

Yes, you need test suite commands to verify correctness before completion, because running them and confirming zero failures provides the required evidence to support your success claims.

A limitation of enforcing strict verification is that every task, code change, or bug fix requires running specific verification commands and analyzing output, which may add overhead to simple updates.