verification-before-completion

To enforce verification before completion, run fresh verification commands, inspect the full output, and confirm the evidence to justify any success claim. This step-by-step workflow prevents misinformation and rework during code reviews and task handoffs.

Claiming completion without fresh verification leads to rework because unverified assertions spread misinformation. Requiring fresh evidence from running verification commands ensures that quality assurance claims are backed by actual output before a task handoff.

The best way to verify code review evidence is to execute the verification routine and provide fresh output for the current task status. This enforces a step-by-step workflow requiring full output inspection before asserting success.

Yes, you can use this verification process for release gating and quality assurance. It enforces a step-by-step workflow suitable for code reviews and PRs, requiring fresh verification evidence to ensure quality before any completion claim is made.

Yes, code verification requires inspecting the full command output before asserting success. The workflow mandates running fresh verification commands and confirming the complete evidence to justify any success claim during a pull request or task handoff.