verification-before-completion

Verifying code correctness before completion requires executing specified commands like tests, linters, or build scripts and analyzing their output to enforce mandatory evidence gathering and prevent false success claims.

Enforcing quality assurance in continuous integration workflows involves executing verification commands and assessing their outputs prior to making success assertions, which reduces errors and false claims during development and deployment.

Preventing incomplete deliverables during code review and deployment requires mandatory evidence gathering by executing verification commands and interpreting their results to validate work completion honestly.

Yes, this verification approach is applicable in development, testing, and deployment workflows, guiding users through executing verification commands and assessing outputs to ensure work correctness and completeness.

Continuous integration builds may pass while deliverables remain incomplete if mandatory evidence gathering and output analysis are not enforced before making success assertions during verification.

To verify work completion before submitting a pull request, you need to execute tests, linters, and build commands, then interpret their results to confirm everything passes and validate completion.