verification-before-completion

To enforce evidence-based verification before claiming a PR is complete, run a defined verification command, evaluate its exit codes and output, and attach the fresh evidence to your success report.

The best workflow to prevent unverified completion claims is a five-step gate process: identify the verification command, run it, read the output, verify the exit codes, and only then claim success with attached evidence.

You need to run verification commands before reporting task completion because claiming work is done without fresh test output or logs leads to unreliable results and dishonesty in your development workflow.

Yes, the verification process works with standard code reviews and release workflows by requiring fresh test output and logs as verifiable evidence before allowing any claims of success to be attached to a PR.

To attach test output as evidence to support a completion claim, execute your defined verification command, capture the complete output and exit codes, and report the results alongside the fresh evidence.

You should avoid relying solely on an automated verification gate for quality checks when you cannot define a specific verification command to evaluate exit codes and generate the fresh test output required as evidence.