verification-before-completion

To enforce verification before completion, implement a structured workflow that requires running a defined command to observe fresh evidence and confirm outputs before updating task status or merging pull requests.

Claiming code is done without running checks increases rework risk because unverified completion claims bypass quality assurance, leading to undetected failures and deceptive status reporting in continuous integration pipelines.

Evidence-based task completion in code review and deployment is a gating mechanism that prevents premature success claims by requiring explicit output review and actual status reporting backed by observed verification results.

To stop premature completion claims in continuous integration, apply a verification workflow that gates progress by requiring a run-check-verify sequence, ensuring tests pass and outputs meet expectations before deployments.

Yes, you can use this verification gating for both code reviews and deployments, as the mechanism applies universally to any task completion or PR scenario where observable evidence must confirm the result.

No specific testing framework is required, but you must define a repeatable command to verify results, carefully review the outputs, and report actual status with evidence before stating success.