verification-before-completion

Verify code changes by executing designated verification commands and reading their outputs to confirm success before making any completion claims. This enforces honesty and correctness by requiring explicit evidence like passing tests or clean exit codes before progressing workflows.

Task verification is the process of validating code and task completion through explicit commands and evidence collection. It prevents inaccurate completion claims by enforcing safety checks, ensuring that success is confirmed through command outputs and exit codes before proceeding.

Enforce safety and quality checks by running designated verification commands and reviewing their outputs to confirm tests pass before submitting a pull request. This validates success through evidence collection, preventing inaccurate completion claims during development workflows.

Yes, verification before completion is suitable for quality assurance contexts. It validates task completion by executing verification commands, reading outputs, and confirming success, ensuring honesty and correctness in both development and quality assurance workflows.

The best way to prevent inaccurate completion claims is to enforce verification by executing specific commands and checking their outputs and exit codes. This requires explicit evidence of success before allowing any task to be marked as complete or progressing workflows.

Task verification fails to catch incomplete code when it lacks enforcement of explicit verification commands and evidence collection. Without reading command outputs and confirming exit codes before claiming success, inaccurate completion claims go unchecked and propagate through workflows.