verification-before-completion

To enforce verification before claiming code completion, apply a strict protocol requiring specific testing, linting, or building commands to run fresh, analyze exit codes, and present tangible evidence before any success assertions are made.

Evidence-based verification for bug fixing and testing prevents premature success claims by requiring tangible command output and exit codes as proof, ensuring actual results match assertions and preventing costly development errors.

The best way to prevent premature claims of work completion in CI/CD is to enforce a strict protocol mandating specific verification commands, analyzing full output and exit codes, and presenting evidence before any task success assertion.

To verify tests pass before committing code changes, identify the specific test suite command, run it fresh, read the full output to confirm zero failures, and only then state completion with the output evidence.

Mandatory verification applies to all stages of software development, including testing, linting, building, bug fixing, and agent task completion, requiring fresh command execution and output evidence before any status claim.