verification-before-completion

To back code completion claims with fresh verification evidence, identify a verification command like a test suite or build, execute it fully, and interpret the outputs to justify the completion status.

Evidence-based completion is a workflow mechanism that prevents premature completion claims by ensuring fresh verification command outputs are captured and recorded before pull requests, merges, or releases.

To enforce running verification commands prior to commits, identify the command that proves completion, run the full set freshly, review exit codes, document failures, and report the actual status with evidence.

Yes, evidence-based completion applies directly to code reviews and pull requests by guiding users to execute verification commands fully, read outputs, and verify that any status claim is supported by fresh evidence.

The best way to prevent premature completion claims during releases is to enforce evidence-based completion by running test suites or builds freshly, capturing outputs for auditability, and justifying statuses with actual results.

No specific test frameworks are required. You can use any existing test suite, build, or lint command as your verification command, provided you execute it fully and interpret the outputs to justify the status.