verification-before-completion

You prevent false success claims by running verification commands and checking fresh output evidence, such as exit codes, before stating work is complete. This enforces a step-by-step process to identify, run, read, and verify commands.

The verification workflow for software testing and building requires executing designated commands, checking exit codes and output evidence, and only then allowing success claims. This stops premature expressions of satisfaction or commit actions.

To verify linting and code review output before declaring a task done, run the designated command, read the fresh output evidence, and confirm the exit code. This prevents rework caused by unchecked assertions.

Your workflow allows commit actions without verification evidence because it lacks a mechanism to block expressions of satisfaction until fresh output is verified. Enforcing command execution and exit code checks eliminates this dishonesty.

Yes, this verification process works with existing CI checks and status updates. It applies to any software development scenario where correctness must be proven before progressing, including testing, building, and linting pipelines.

You need to run verification commands before a completion status update whenever a task requires correctness to be proven. This ensures every completion statement is backed by fresh verification evidence, reducing false positives.