verification-before-completion

To verify code changes before claiming completion, you must execute the full verification command, evaluate its output, and confirm exit codes show no failures. This enforces evidence-based QA workflows by requiring fresh proof before asserting success.

Evidence-based verification in software QA is a strict protocol requiring execution of verification commands and evaluation of their outputs before any completion claim is made. It prevents false success claims by demanding fresh output as proof during code review.

You stop false success claims during code review by enforcing a step-by-step verification workflow. This process requires running the full verification command, reading its output, and validating exit codes to ensure completion claims are backed by fresh evidence.

The verification workflow requires executing the full command and reading its output, not just checking the exit code. It enforces a strict protocol to identify the verification command, execute it fully, and verify the results before making any completion claim.

You need to run verification commands before merging a pull request whenever you intend to make a completion claim. The workflow enforces executing the command fully and evaluating the output to provide fresh evidence that proves the claim is valid.

The limitation of enforcing a strict verification workflow is that it requires fully executing the verification command and reading the complete output every time a completion claim is made, which may add overhead to the pull request and code review process.