verification-before-completion

Verification before declaring a pull request complete requires running explicit verification commands and validating their outputs as fresh evidence. This structured gate ensures evidence-based assertions and prevents dishonest completion claims during PR finalization.

Evidence-based verification for code review readiness is a gating mechanism that executes verification commands and checks outputs before claims. It provides fresh proof of success, satisfying quality-assurance requirements prior to handovers or PR submissions.

Documenting verification evidence for software handovers involves executing required verification commands and capturing their outputs through a structured gate function. This validates the current task status against requirements before making completion assertions or final handovers.

This verification process applies to general software development workflows during finalization, PRs, and handovers. It functions in any context requiring verification commands to be run and their outputs checked against requirements before declaring completion.

Running verification commands before claiming task completion prevents dishonest or inaccurate success claims. Enforcing an evidence-based gate ensures that the work is validated against requirements using fresh output data before finalization.