verification-before-completion

Preventing false completion claims requires running the exact verification command, checking exit codes and failure counts, and ensuring your success wording matches the fresh output evidence before committing or opening a pull request.

Evidence-first completion gating is a workflow that forces you to identify, run, read, and verify the exact command output before claiming a pull request is ready, ensuring tests, lint, and build success statements are backed by fresh evidence.

You stop premature success claims by enforcing a strict verification workflow that blocks rationalizations like "should pass" or trusting agent reports, requiring fresh command output and exit code checks before any completion status is declared.

Yes, you can use automated verification to check lint and builds before a PR by enforcing a workflow that runs the full command, reads the fresh output, checks the exit code, and only then allows you to claim the work is complete.

You need fresh command output before claiming a bug fix is complete because trusting agent reports or partial checks without verifying the exact exit code and failure counts leads to misleading success wording and unverified claims in your status updates.