verification-before-completion

Yes, verification before completion applies to regression checks and PR readiness communications. It ensures that any satisfaction statement or completion announcement is backed by fresh command output and a passing exit condition.

Evidence-based verification is a workflow requiring fresh command output and a passing exit condition before asserting task success. It prevents premature completion claims by ensuring tests, linting, and builds are substantiated by actual current results.

To enforce a verification gate for build readiness, identify the exact proving command, run the full check fresh, and review the complete output. You can only claim success after confirming a passing exit status with concrete evidence in hand.

Asserting linter cleanliness without full output causes problems because it relies on assumptions rather than current facts. Verification before completion blocks this failure mode by requiring fresh lint output and a confirmed passing exit code before reporting success.

Yes, you can use this verification workflow with your existing testing commands. It requires no specific dependencies and works by enforcing that your current test, lint, and typecheck commands are run fresh and produce a passing exit status.

You should run release gating checks during software engineering workflows whenever you are about to finalize work, commit, or open a PR. This ensures your completion announcements and readiness communications are backed by fresh verification evidence.