verification-before-completion

To enforce verification before claiming a PR is complete, you require running verification commands and validating fresh outputs to prevent unverified success. This ensures evidence is gathered and confirmed before any status changes or PR approvals are made.

Evidence-based quality assurance for task handoffs is the process of requiring fresh verification outputs, such as passing tests or lint checks, before declaring a task complete. It prevents unverified success claims by ensuring all checks pass before status changes.

To run and validate test and lint outputs before committing code, you execute the verification commands and read the outputs directly. You only declare success or proceed with the commit after confirming that all fresh verification checks have passed.

Yes, you can use verification checks for development workflows and code reviews. The process applies to PR reviews and task handoffs, applying to development workflows by requiring fresh verification evidence and confirming all checks pass before making success claims.

Requiring verification before completion prevents unverified success by enforcing that fresh verification evidence is gathered and validated before status changes. It mandates running commands and reading outputs, ensuring success is only declared when all checks pass.