verification-before-completion

To verify code changes before claiming task completion, run the provided verification commands and ensure the output confirms success before making any claims. This enforces evidence-based practices for work completion.

Evidence-based work verification for pull requests requires concrete command output to back any completion, fix, or passing claims. This process prevents false success assertions and promotes accountability in project phases.

Prevent false completion claims during code review by following a structured step-by-step verification process. Manually verify command outputs to ensure work is complete before making any success claims.

Yes, you need to manually run verification commands to verify work completion. The process requires manual verification of command outputs to mitigate the risk of dishonesty and ensure claims are evidence-driven.

Use a structured verification process for task completion during any project phase where completion claims are made, such as code reviews, pull requests, or task completions, to ensure honesty and accountability.