verification-before-completion

To enforce verification before claiming a PR is complete, require fresh evidence and full verification command outputs. This process ensures claims are backed by evaluated results rather than assumptions, establishing accountability during code reviews and commits.

The process to require evidence before reporting task completion is a repeatable gate: IDENTIFY, RUN, READ, VERIFY, and REPORT. This sequence enforces running a designated verification command and evaluating its complete output before confirming any success status.

PR quality assurance does not work effectively without fresh verification evidence. Requiring full verification command outputs during code reviews prevents unverified completion claims, ensuring transparent and accountable development practices across your team.

The best way to gate code commits is enforcing a strict verification sequence: identify the command, run it, read the complete output, verify the results, and report with supporting evidence. This prevents developers from skipping quality assurance checks.

A limitation of enforcing evidence-first completion claims during code reviews is that it requires running a designated verification command every time. Teams must consistently evaluate the full output to maintain transparency and avoid reverting to unverified status reporting.

You can use this verification gate process for both code commits and pull requests. The enforcement applies to any work completion claim, requiring you to run designated verification commands and evaluate full outputs before reporting a confirmed status.