verification-before-completion

To prevent premature claims of code completion, enforce a strict verification protocol that requires running specific commands, reviewing their output, and presenting evidence before asserting any success or correctness.

The evidence before claims principle in quality assurance mandates that you run and verify command outputs proving a status, such as passing tests, before making any positive assertion about work correctness.

To verify bug fixes before declaring task completion, identify and run the command that proves the fix, read its full output, confirm the outcome matches expectations, and then make the claim with evidence.

Yes, verification before completion is applicable to all stages of software development and task completion, ensuring factual accuracy and preventing incomplete or broken work from shipping.

You need to run test suites before claiming a successful build to catch issues early through rigorous validation, reducing rework and ensuring the output confirms the success statement factually.

The best way to enforce mandatory verification during code review is to require running relevant test suites or reproduction commands, reviewing their output, and presenting factual evidence before any success statement.