skill-verify

To enforce evidence-based verification, run a structured verification sequence that captures full command output, validates exit codes, and confirms success only with verifiable proof. This prevents declaring completion without executing required checks.

An evidence gate is a strict validation mechanism that requires executing verification commands, reading outputs, and validating exit codes before allowing status changes. It ensures claims like ALL PASSING are backed by captured proof during releases.

Yes, automated verification gating applies to manual QA task closures by guiding teams through identifying verification commands, running them, and confirming claims with evidence. It works across both CI/CD workflows and manual checks.

To verify code review claims before approving a commit, execute the necessary verification command, review the full output, and validate the exit code. Success is only claimed when captured evidence confirms the verification results.

The best way to prevent declaring success without verifiable proof is enforcing a strict evidence gate on every status change. This requires executing checks, capturing output, and validating exit codes before confirming completion across workflows.

Your verification sequence fails to gate task closures properly if it does not enforce capturing full command output and validating exit codes. A strict evidence gate must require verifiable proof before allowing any status change to DONE.