ferrox-verification-before-completion

To prevent false completion claims before creating a pull request, enforce a verification gate that requires running tests or builds immediately and reviewing the exact command output and exit code before stating any success.

A verification gate in software engineering workflows is a quality checkpoint requiring fresh execution evidence, such as test or build outputs, before allowing status updates, commits, or task handoffs to prevent relying on stale results.

To verify fresh test output before claiming a bug fix is complete, directly execute the relevant testing command, review the printed output, and confirm a successful exit code immediately prior to making any success statement.

Yes, you can use verification checks for both git commits and task handoffs. The process applies to coding workflows involving tests, builds, and regression checks, requiring direct command execution and exit-code confirmation before status updates.

The best way to stop agents from relying on stale build results is to implement a completion gate that mandates fresh verification evidence and direct output review before allowing any claims that a build is passing or ready to ship.