verification-before-completion

Ensure code review honesty by mandating a strict verification protocol that requires running specific commands, analyzing their fresh output, and presenting concrete evidence before making any success assertions.

Verify test suite passing by running the specific test command, reading its full output, confirming all tests pass based on the fresh execution, and then stating the completion claim with that evidence.

Evidence-based verification is a strict protocol requiring concrete command output and exit codes to support any statement about work status, ensuring accuracy in reporting and preventing dishonest claims of correctness or completion.

Enforce running verification commands before reporting work status by implementing a mandatory protocol that identifies the command proving the claim, executes it, reads the full output, and verifies the output confirms the claim.

Claiming code is fixed without fresh verification output causes issues because it relies on assumptions or previous runs rather than concrete evidence, leading to premature declarations of success and inaccurate work status reporting.

No specific testing frameworks are required to enforce completion verification, as the protocol mandates identifying and running whatever specific verification commands prove the claim within your current environment.