verification-before-completion

To verify code changes before claiming task completion, you must execute explicit validation commands like tests or builds and analyze their outputs. This enforces honesty and prevents false success claims by requiring concrete evidence of passing checks.

Skipping validation steps leads to false success claims because developers may report task completion without running tests or builds. Enforcing verification through evidence prevents these inaccurate reports and promotes accountability in software quality workflows.

The best way to enforce test execution before merging is to require running explicit verification commands and reviewing their outputs. This ensures all unit tests pass, confirming code quality and stability before integration into the main branch.

Yes, you can use verification commands for code review and quality assurance workflows. The process requires executing and analyzing validation outputs to confirm task completion, which is applicable across testing, reviewing, and ensuring overall software quality.

Yes, you need to run specific builds or validations to prevent premature progression in software testing. Executing these verification commands and analyzing their outputs stops dishonest claims by confirming that all essential checks actually pass.