verification-before-completion

Preventing premature task completion requires enforcing verification checks that demand up-to-date command output, exit codes, and logs confirming successful execution before finalizing any task.

The best way to verify code review evidence before marking an issue as done is to run specific verification commands and inspect recent logs to ensure tests passed and configurations succeeded.

You can enforce test verification in deployment processes by requiring specific verification commands to run successfully and checking that recent logs display current, successful execution results before proceeding.

Yes, verification enforcement integrates with automated code review workflows by checking that verification commands with exit codes and logs have been run before declaring task completion.

You need up-to-date logs to confirm successful execution because current verification evidence maintains quality assurance and accountability by proving the latest test run actually passed.

You should not rely on automated verification before completion when you cannot run specific verification commands or inspect recent logs, as current evidence is required to confirm successful execution.