verification-before-completion

To verify code changes before completion, run the project's test suite, collect command outputs, and validate that bug fixes or features meet stated requirements. This evidence-based approach prevents prematurely closing tasks or pull requests without concrete proof of success.

Evidence-based reporting in CI-CD and QA workflows requires attaching validation logs and test results to task closures. It shifts teams away from assumptions by enforcing that command outputs and test results are collected as auditable proof before deployment handoffs.

To validate deployment handoffs before closing a release, execute verification workflows and capture exact test outputs as evidence. This ensures that code changes meet stated requirements and provides auditable progress for quality assurance.

Yes, verification before completion works for bug fixes and feature implementations. The process applies end-to-end verification across development workflows by requiring test results and validation logs to ensure changes meet stated requirements.

The best way to enforce quality assurance during code review is to require validated outcomes rather than assumptions. Demand concrete evidence like command outputs and test results to verify work is actually done before approving pull requests or releases.