verification-before-completion

To enforce verification evidence before completion, you must run the full verification command, evaluate its output, and report the final status only with concrete evidence of the results.

The best way to prevent premature completion claims in a CI workflow is to apply a repeatable verification process that requires fresh evidence from your tests and lint checks before success is declared.

To verify QA checks before merging a PR, identify your verification suite, run it fully to generate concrete evidence, and declare success only if all checks pass with clear output.

Yes, you can use this to enforce a repeatable verification workflow for software development by ensuring you identify the verification command, execute it fully, and evaluate the output before reporting status.

You need fresh verification evidence for quality assurance tasks to prevent dishonest status updates and guarantee verifiable results, ensuring work is never claimed complete without running the full verification suite.