verification-before-completion

To enforce verification before declaring a pull request complete, run explicit verification commands and collect their outputs. This ensures completion claims are substantiated by verifiable evidence prior to PR creation or code review.

Evidence-based completion in software development is a process that requires running explicit verification steps and collecting outputs to substantiate claims before declaring work complete, fixed, or tested.

To generate audit-ready logs for code reviews, run prescribed verification commands and review their outputs to ensure all tests pass. Attach these verifiable artifacts to your PRs before merging.

Yes, this verification process works with release workflows by enforcing that verification commands are executed and documented. It generates verifiable artifacts that can be attached directly to releases.

The best way to prevent unverified completion claims is to enforce running explicit verification steps and require evidence-backed final statements that validate claims with verifiable outputs before submission.