verification-before-completion

To enforce test verification before declaring a pull request complete, apply a five-step gate function that identifies, runs, and reads the full verification command output, ensuring all exit codes and reproducible checks pass before claiming success.

The best way to prevent false claims about passing builds is to require fresh, observable verification evidence such as command outputs and exit codes before asserting that work is done, eliminating premature or unverified success statements.

To verify code quality checks before committing changes, run the exact verification command for the task, inspect and copy the full output including the exit status, and report that evidence before stating anything has passed.

Yes, you can use pre-release verification for CI checks and agent delegations by applying an evidence-first reporting pattern that requires running the full verification command and examining outputs before accepting agent-reported success or merging branches.

Bug fixes fail CI checks after being declared resolved because of premature assertions without fresh verification evidence, requiring you to capture red flags, prevent rationalizations, and ensure reproducible proof like test outputs and build exit codes before claiming completion.