verification-before-completion

To enforce verification before declaring a software build complete, this Skill requires fresh command outputs as evidence. It validates exit codes and documents verifiable proof for status claims, preventing premature success declarations in your workflow.

Command-driven verification in CI-CD pipelines is the process of running prescribed commands and validating their outputs before any release checks pass. This mechanism ensures reliable success claims by attaching fresh execution evidence to every status update.

To attach verifiable evidence to PR reviews, run the prescribed verification workflow commands and include their fresh outputs in your completion claims. This validates test results and exit codes, providing documented proof that requirements were met.

Yes, this verification approach works for deployment pipelines across different platforms. It applies broadly to software development workflows, validating builds, tests, and release checks by enforcing command-driven output validation regardless of the specific environment.

You need fresh command outputs for quality assurance status claims to guard against unreliable success declarations. Requiring current execution evidence ensures that prescribed verification commands actually pass at the time of completion, preventing stale validation.

The best way to prevent premature releases during code review is to enforce an automated verification gate requiring fresh command outputs. This mechanism validates exit codes and documents evidence before any completion claim is accepted, ensuring only verified changes proceed.