verification-before-completion

To enforce verification evidence before a pull request is merged, you must run a complete verification command, capture its output, and attach the results to the PR as proof of code quality. Success is reported only when this evidence confirms the claim.

To prevent premature completion claims in CI/CD pipelines, enforce a workflow that requires running a complete verification command during finalization and reporting success only when fresh output confirms the work is actually verified.

To attach test results as evidence to code changes, you run the verification workflow across your software development process, analyze the output, and attach those results directly to your commits or pull requests before signaling completion.

Yes, the verification process works without any external dependencies, requiring only your existing software development workflows and a complete verification command to capture fresh evidence before finalizing code changes or releases.

You need to run a verification command before signaling code release completion whenever finalizing code changes or pull requests, ensuring that every completion claim is backed by fresh, verifiable evidence confirming the work is actually verified.