verification-before-completion

To verify test results before committing, you must execute the full verification command, capture the complete output and exit code, and inspect that evidence to confirm success before declaring work complete.

A verification gate is a five-step process to identify the verification command, run it fresh, read the full output and exit code, verify results, and only then claim success to prevent false completion claims.

Prevent false claims of passing tests by enforcing that verification commands are actually run and their full outputs, along with exit codes, are inspected and attached as evidence before asserting any positive status.

The best way to enforce regression testing verification before opening a pull request is to run the project's verification command, capture the exit code and full output, and provide that evidence before reporting completion.

Yes, verification before completion applies across development workflows including lint checks and building artifacts, requiring you to execute the verification command and inspect the full output before claiming success.

You need to attach command output evidence for agent-delivered changes whenever reporting status, ensuring you execute the verification command, capture the exit code and output, and provide it as proof before stating the work is complete.