verification-before-completion

To enforce verification before completion, you need a gate that mandates running test, build, or lint commands and parsing their outputs to validate exit codes. This ensures every completion claim is backed by fresh, verifiable evidence rather than premature assertions.

Attaching test and lint evidence to code review claims requires capturing the complete output of verification commands and reporting it alongside the final status. This evidence-first discipline prevents dishonest status reports by validating exit codes before asserting success.

The best way to prevent premature status reports is implementing an evidence-based verification gate that blocks completion claims until fresh test, build, and lint results are captured and validated. This enforces accountability by requiring verifiable proof before any success assertion.

Yes, this verification gate is designed for release workflows and PR approvals where tasks must pass tests, lint, and build checks before being marked complete. It validates exit codes and presents a final claim with attached evidence, ensuring only verified changes proceed.

Task completion claims fail without fresh verification evidence because the system enforces an evidence-first discipline that blocks dishonest or premature status reports. It requires running verification commands, parsing outputs, and validating exit codes before accepting any success assertion.

Before claiming a build is successful, you should capture complete outputs from verification commands including test results, build status logs, and lint reports. Validating their exit codes ensures your completion claim is backed by verifiable evidence rather than assumptions.