verify-before-done

To prevent false completion claims during code reviews, enforce fresh verification outputs before asserting that a task is done. This requires running tests, syntax checks, and git state checks to provide a structured report validating actual progress.

You need evidence before claiming a software release is ready because a claim without verification is a guess. Requiring fresh test outputs and a clean git state guards against premature or unsubstantiated progress claims.

Requiring verification outputs improves workflow quality by enforcing evidence before assertion. It ensures teams run commands and show successful test outputs and clean git states before stating any task is complete, fixed, or ready.

Yes, you can use this verification guardrail for merges and releases. It applies to any workflow where teams claim tasks are done, enforcing fresh checks and providing a structured report to validate progress before completion assertions.

The best way to verify task completion with evidence is to always run the verification commands and attach their actual outputs before stating a task is complete. This prevents false claims by validating progress with fresh check results.