verification-before-completion

To prevent false completion claims before committing code or creating pull requests, enforce a mandatory verification gate that requires running fresh full verification commands, reviewing the complete output, and confirming evidence supports all success claims before stating any task is done.

Code shipments break because trusting past test runs or assuming linter passes mean builds succeed creates false positive status reports. Explicitly listing insufficient verification scenarios prevents skipping verification and ensures requirement compliance before marking work complete.

The best way to enforce verification before task completion is applying a 5-step process: identify the relevant verification command, run it fresh, read the full output, confirm claim validity against the results, and then state the completion status with supporting evidence.

To stop rationalizing skipped tests and validation during software development workflows, directly counter common excuses like being confident or skipping checks just this once to enforce consistent adherence to verification rules before any code commits or pull request creation.

Mandatory verification before completion works for bug fixes and regression testing by requiring you to run the full regression test suite, confirm the original symptom is resolved, and verify no new failures appear before marking the bug fix task complete or opening a PR.

You need mandatory commit validation in your development workflow whenever preparing to commit code, create pull requests, delegate agent tasks, or validate builds and requirement compliance to eliminate the risk of broken code shipments and wasted rework from skipped verification.