verification-before-completion

The best way to verify a bug fix is resolved is to run the exact validation command and read the full output and exit code. This verification process ensures you only report success when fresh evidence confirms the fix actually passes.

Pre-commit verification requires reading the full command output and exit code to validate the actual status. This validation process ensures you report only evidence-backed results rather than assuming the build checks or tests passed successfully.

You can use requirement validation checks for pre-PR status updates by running the exact proof command to verify the current state. This quality assurance process ensures your status update is backed by fresh test or build evidence.

Build verification fails without checking the exit code because you cannot confirm the actual success of the test or build checks. Reading the full output and exit code guarantees the completion claim is strictly evidence-backed.