verification-before-completion

To prevent unverified completion claims, enforce a verification gate requiring you to run specific test commands and present their output as evidence before marking any bug fix or task as complete.

A verification gate in CI/CD workflows is a strict checkpoint that mandates identifying, running, and verifying the output of specific commands to provide concrete evidence of success before any completion claim is accepted.

To verify successful test execution before marking a ticket resolved, run the specific test command that previously failed, confirm it now passes, and provide the fresh command output as evidence of the fix.

Yes, enforcing verification before completion applies to all stages of development and deployment where completion is asserted, preventing unverified claims and ensuring code quality across the entire workflow.

You need to run verification commands for premature completion assertions to prevent the costly mistake of shipping broken code or incomplete features, thereby reducing rework and maintaining trust in the codebase.