verification-before-completion

To verify code changes before committing, you must run full test suites, lint checks, and build commands, then read the outputs and check exit codes. This enforces a step-by-step protocol to confirm actual state with documented evidence before claiming completion.

The verification process for pull requests involves identifying required checks, running full verification commands, reading outputs, checking exit codes, and reporting the actual state with concrete evidence before asserting any success claims.

Enforcing verification checks before claiming a task is done prevents delivering unverified work. It guards against red flags suggesting incomplete status and requires concrete evidence like test and build outputs to support any completion claims.

To support a success claim before merging, you need concrete evidence from running full test suites, lint checks, and build verifications. This includes reading outputs, confirming exit codes, and documenting the actual state across multiple projects.

Yes, this verification workflow applies to development workflows across multiple projects. It ensures running full verification commands, reading outputs, checking exit codes, and reporting the actual state with evidence before commits and pull requests.