verification-before-completion

To prevent unverified completion claims, implement a verification gate that identifies the designated test command, executes it fully, and analyzes the output before marking work complete. This ensures fresh verification evidence is always attached prior to any success claim.

The best way to require evidence before approving a PR review is to run a verification gate that executes build and test commands, then reports the outcome with verifiable logs and exit codes. This prevents merging code without fresh verification evidence.

A verification gate analyzes build and test output by identifying the command that proves completion, running it fully, and assessing the resulting logs and exit codes for success. It then reports the outcome with evidence before any completion claim is made.

Yes, you can use this verification gate for release gates beyond PR reviews. It applies to any development workflow where tests, builds, and checks must pass before marking work complete, ensuring fresh verification evidence is provided prior to success claims.

No specific continuous integration dependencies are required to run verification checks. The gate works by identifying your designated verification command, executing it within your environment, and attaching the resulting logs as evidence before claiming completion.

You should attach verification logs before marking a task done to ensure tests, builds, and checks have actually passed. This evidence-first reporting prevents unverified completion claims by providing verifiable results like exit codes and diffs prior to success.