verification-before-completion

Enforce verification evidence by running full test, build, and lint commands, then examining their outputs and exit codes before declaring a pull request complete. This gate function prevents dishonest completion claims by requiring auditable proof of success.

Verifying test and build success requires running the full verification commands and checking their exit codes and outputs. This approach ensures you have fresh, reproducible evidence before asserting that your code is ready to merge.

Running fresh builds and tests is necessary because claiming completion without verification is dishonest. This process provides auditable evidence from actual command outputs and exit codes, ensuring reproducibility before merging or releasing.

Set up a gate function by running your verification commands, reading the outputs, verifying the exit codes, and only then claiming success. This step-by-step process ensures lint and test results are examined before completion is declared.

Yes, you can use this verification gate for any codebase or team that requires auditable, reproducible completion evidence. It works across tests, builds, lint, and pull-request workflows to enforce honest reporting before merging or releasing.

Asserting completion without fresh verification outputs leads to dishonest claims and unverified code. The limitation is that you lack reproducible evidence from test, build, and lint exit codes, risking failure when merging or releasing.