verification-before-completion

Verification before completion means running your build or test commands fresh, reading the full output, checking exit codes, and confirming success before pushing or opening a PR. Only make completion claims when you have current evidence in hand, not assumptions.

Enforce a verification gate: identify the right command for your project (build, test, lint), execute it, review the output completely, and verify the exit code signals success. This 5-step cycle catches failures before they reach PRs or merges.

Run fresh verification before each boundary: before committing work, before pushing to a branch, and before opening a PR. Verification at every gate prevents incomplete or broken code from advancing through your workflow.

Yes. Running verification fresh each time—not relying on earlier test results—catches state changes, dependency shifts, or environment drift that earlier runs missed. Fresh output always reveals the current truth.

Without verification evidence, you risk pushing broken code, failing CI/CD pipelines, or merging incomplete work. Verification enforces accountability: no completion claim without output proof.