verification-before-completion

Verification before completion enforces evidence-based checks by running a 5-step workflow. It identifies proof commands, executes them, checks output and exit codes, and reports status to prevent premature task completion claims.

To generate evidence before pushing a PR, run a verification workflow that executes test commands, checks exit codes, counts failures, and reports success status with concrete output evidence.

The verification gate process works by defining a full workflow that identifies required proof, executes it fresh, reviews command outputs, checks exit codes, and reports verifiable status before allowing any release completion claims.

Yes, you can use verification steps to prevent unsafe releases. The process enforces a strict 5-step gate that requires successful command execution and evidence review before allowing any completion assertions.

Validating command output and exit codes requires defining a verification workflow, executing the proof command fresh, reviewing the generated outputs, checking failure counts, and reporting the final status with evidence.

You should run a verification workflow because it enforces evidence-based completion by checking command output, exit codes, and failure counts. This prevents unsafe or premature releases by guaranteeing status claims have verifiable proof.