verification-before-completion

To enforce code review verification before claiming work completion, use a structured workflow that requires evidence of passing tests, clean linters, and successful builds to validate any success statements.

Evidence-based verification for software development workflows is a process that prevents dishonesty by requiring concrete proof of verification steps and outputs before allowing any claims of work completion or success.

You verify pull request readiness by running a structured verification command that checks all tests pass, linters are clean, and build steps are successful, requiring the resulting evidence to back any completion claims.

No, evidence-based work completion verification requires no external dependencies, functioning as a standalone process to enforce validation through identification, execution, and verification of claims.

You need evidence-based verification in release preparation when you must guarantee high-quality deliverables by preventing unverified success statements and requiring proof that all build steps and tests are successful.

The best way to prevent dishonest completion claims during code reviews is to implement a verification workflow that enforces evidence-based validation, rejecting any success statements that lack concrete proof of passing tests and clean linters.