verification-before-completion

To prevent unverified completion claims, require executing the full verification command and checking exit codes or failure counts before reporting a task as done, fixed, or passing.

The best way to verify code review changes is to run the exact verification command for the current state, read the output and exit codes, and cite that fresh evidence before stating success.

Yes, this verification approach works with debugging, build validation, commit readiness, and PR preparation workflows by forcing results to be confirmed in the current run before any success is reported.

You can use this to require fresh evidence by executing the full testing or debugging verification command, reading failure counts, and citing the current run's output before claiming a fix is passing.

Requiring fresh evidence for build checks prevents false confidence, missed regressions, and incomplete handoffs by ensuring the verification command output and exit codes are confirmed in the current run before success is stated.