verification-before-completion

To prevent false completion claims before opening a pull request, you must run the exact verification command and inspect its full output before asserting that work is done or ready to ship.

Evidence-first build validation is a process that requires running fresh verification commands and reading their full output to confirm status, ensuring you only state success supported by actual results.

To verify bug fixes using actual command output, run the relevant test or build command, read the complete output, and report only what the fresh execution results confirm rather than making unsupported claims.

Yes, you need to run tests before claiming a requirement check is passing. The workflow requires executing the relevant command and reading its full output before making any positive status assertion.

Yes, you can use this verification workflow for pre-commit validation. It applies directly to pre-commit and pre-PR validation workflows by forcing you to run verification steps before reporting success.

The best way to ensure quality assurance claims are supported by fresh evidence is to require running the exact verification command and inspecting its full output before stating any task is fixed, passing, or complete.