verification-before-completion

Verify code changes with fresh evidence by identifying the exact command that proves completion, executing the full verification workflow, and reporting status only after parsing the actual output and exit codes.

Evidence-first verification is a workflow that requires running the full verification command and capturing complete outputs to prevent premature success claims during CI builds, code reviews, and task handoffs.

Prevent premature success claims during task handoffs by applying a verification workflow that requires executing the full command, parsing the output, and reporting status with explicit reasoning when checks do not pass.

Yes, you can use this verification workflow for both builds and code reviews, as it applies an evidence-first approach to ensure all checks pass before marking any work complete across different software engineering contexts.

When verification checks fail before marking work complete, you should present the actual state with supporting evidence and explicit reasoning rather than claiming success, ensuring all failures are clearly reported.

Identify the exact command that proves a completion claim by determining what constitutes a successful verification for your specific task, then executing that full command to capture and evaluate the complete output.