verification-before-completion

To verify code review claims before declaring a PR complete, run the exact verification commands on the current task and parse the fresh output. You must validate exit codes and report this evidence before updating status or claiming completion.

A verification gate in a CI pipeline is an enforced checkpoint that requires running fresh verification commands and reporting evidence before declaring success. It ensures completion claims are substantiated by validated exit codes and parsed output.

To prevent faulty releases from unverified completion claims, enforce a verification gate that runs required commands and interprets results before any release readiness declaration. This ensures evidence is produced and validated before success is claimed.

Yes, this verification approach works with CI workflows and quality gates by specifying a fresh verification command, parsing its output, and validating exit codes. It is designed for software development workflows where completion claims must be verified.

You need to run fresh verification commands for release readiness whenever a completion claim is made. This ensures the evidence is current and accurate, preventing misstatements by requiring you to parse output and validate exit codes before declaring success.

Completion claims are unreliable without verification because they lack substantiated proof. By enforcing a verification gate that requires running exact commands, parsing output, and validating exit codes, you produce the evidence needed to prevent misstatements and faulty releases.