verification-before-completion

To enforce verification before closing a pull request, run full validation commands like tests and linters, interpret the outputs, and attach concrete evidence prior to making any completion claim.

Preventing premature completion claims requires a structured verification process that executes checks on code changes and documentation, demanding irrefutable evidence before allowing any success statements or ticket closures.

Verify code changes and documentation updates by executing step-by-step checks, interpreting the validation results, and reporting the evidence to satisfy requirements prior to declaring a task complete.

Yes, structured verification applies to post-implementation checks and releases, enforcing the execution of full verification commands and interpretation of outputs before any success assertions are made.

Attaching verifiable evidence before claiming a release is successful eliminates dishonest assertions by ensuring all required checks are executed, interpreted, and reported prior to any success statements.

Yes, verification before completion works without external dependencies, using its advanced internal reasoning to enforce guardrails and interpret validation outputs directly within your workflow.