verification-before-completion

To prevent false completion before a pull request, you must execute defined verification commands, review the full outputs, and only declare completion with supporting evidence. This ensures claims are backed by verifiable test results.

Verification before completion is a validation process requiring developers to run structured testing commands and attach output logs as evidence before declaring any code changes or task closures done.

To ensure quality assurance evidence during code review, run complete verifications across your software development workflow and explicitly attach the output logs to your pull request to satisfy structured validation requirements.

Yes, this verification process works without external dependencies by applying an internal validation mechanism that requires reviewing explicit success criteria and command outputs before closing tasks or merging code.

You need to run validation commands for task closures whenever you claim work is finished, a bug is fixed, or tests pass, ensuring you collect verifiable evidence before the final submission.

The best way to avoid false completion is enforcing a strict workflow that requires running verification commands, reviewing full outputs, and presenting explicit success criteria as evidence before declaring any task done.