verification-before-completion

To verify code completion before a pull request, run fresh verification commands across the codebase, evaluate full outputs and exit codes, and report results with evidence before asserting success.

Claiming work is complete without verification leads to deployment risks because it allows silent defects to bypass quality assurance checks, requiring evidence-backed validation of command outputs to preserve deployment integrity and accuracy.

The best way to validate pull request outputs before committing is enforcing the practice of running fresh verification commands, capturing their outputs across the codebase, and validating exit codes before reporting success.

Yes, verification before completion works for general code review milestones by applying the practice of executing verification commands and collecting evidence-backed results to prevent premature completion statements during commits and pull requests.

To capture verification evidence across the codebase before asserting success, run required verification commands, evaluate full outputs and exit codes, and report collected results to validate completion claims.