verification-before-completion

To enforce verification before claiming a pull request is complete, you must run the full verification command, collect the output as evidence, and report pass or fail status with supporting data before triggering a commit or merge.

Evidence-based verification in a CI-CD workflow is the process of executing explicit verification steps and gathering fresh output data to prove quality assurance gates are met before a completion claim triggers a build or release.

You need to run verification commands before merging code to protect integrity and reduce regressions by ensuring that fresh test outputs and quality gate results validate the completion claim before a PR proceeds.

Yes, you can use automated verification gates for tasks outside of code review by applying this evidence-based process to any task with a required verification gate before triggering completion claims, builds, or releases.

The best way to collect verification evidence for quality assurance is to execute a repeatable verification cycle that runs the required commands, captures the full output, and reports the pass or fail results with supporting evidence.