verification-before-completion

To enforce verification before claiming code completion, you must run defined commands like tests and linters anew, evaluate their outputs and exit codes, and report the evidence before updating status. This prevents premature completion claims without fresh proof.

A verification gate workflow in CI and PR readiness is a process that requires running fresh builds, tests, and lint checks, then attaching their command outputs as evidence before declaring success. It protects against inaccurate status claims and rework.

To provide evidence-based reporting for passing tests and builds, you run the required verification commands, capture their full outputs and exit codes, and state the actual status with that fresh evidence prior to making any completion claim.

No specific dependencies are required. The verification workflow applies across codebases using your existing defined commands for testing, linting, and builds, requiring only fresh command outputs and exit codes as proof before asserting success.

You should not skip a verification gate before commits or releases if your workflow demands verifiable readiness. It is essential whenever making completion, fixation, or passing status claims to ensure you have fresh command outputs as proof.