verification-before-completion

To verify code changes before completion, identify a verification command, run it fully, read the output and exit code, and verify the result before claiming success. This enforces evidence-based validation and prevents premature success announcements in CI pipelines.

The verification protocol involves identifying the verification command, executing the full verification, reading the complete output and exit code, verifying the results, and reporting the actual state before asserting success. This ensures all completion claims are backed by fresh evidence.

Prevent premature success announcements in code reviews by requiring fresh verification evidence before declaring fixes or passing status. Guide teams to execute verification commands and review actual outputs before committing changes or opening PRs.

Yes, evidence-based verification applies to software development, CI pipelines, and code reviews. It requires tests, builds, or fixes to be backed by verifiable command outputs, ensuring honesty and reliability across QA processes by gating completion claims on fresh evidence.

Asserting success without full verification risks unseen failures and false completion claims. Without reading the complete command output and exit code, teams lack the fresh evidence needed to guarantee reliability, increasing the risk of premature success announcements and undetected issues.