verification-before-completion

To prevent false completion claims in pull requests, require fresh verification evidence by identifying a proving command, running it, validating exit codes, and checking failure counts before asserting success.

Evidence-based verification is a workflow pattern that rejects satisfaction language and success implications unless directly supported by the latest full command output and exit status.

To verify tests and builds before committing code, identify the specific proving command, run the full command, validate the exit codes and failure counts, and only then claim completion.

Treating partial checks as proof causes unreliable bug-fix confirmation because linting or compilation alone does not verify testing success, leading to dishonest or unverified status assertions.

No, you do not need CI/CD pipelines to enforce verification gatekeeping. You can apply this command-identify, run, read output, and verify pattern locally before committing or opening pull requests.