verification-before-completion

To verify code changes before claiming completion, you must run fresh verification commands like tests or lint, inspect the output and exit status, and declare success only when the evidence confirms the claim.

Preventing premature completion claims in pull requests requires enforcing a strict verification gate that runs builds and tests fully, ensuring outputs are fresh and trustworthy before declaring success.

Requiring fresh evidence improves release readiness by enforcing a stepwise process to identify the verification command, execute it, read outputs, and only claim success when verifiable results confirm the work.

You need to run verification commands before committing code whenever you are about to claim work is complete, fixed, or passing, ensuring that assertions are always backed by fresh outputs from tests or builds.

Claiming a fix is passing without inspecting the test output is not allowed; the verification process requires identifying the command, running it fully, and checking the output and exit status before declaring success.

Yes, the verification process works with lint and build checks, covering scenarios where claims must be backed by verifiable results across tests, lint, and builds before declaring completion.