verification-before-completion

This skill enforces verification before claiming completion by requiring fresh verification outputs. It applies a gate-based approach to identify, run, read, and verify checks before permitting any success claims for pull requests or commits.

Evidence-first completion is a quality assurance process requiring fresh verification outputs before any success claims are made. It guards against unchecked assumptions by enforcing that tests and checks pass with explicit evidence before finishing a software task.

To stop unchecked assumptions when preparing commits, apply a verification gate that runs full verification commands and examines outputs before permitting success claims. This ensures completion claims are supported by explicit verification results.

Yes, this verification gatekeeping applies to any software task or code changes where pull requests, commits, or releases are prepared. It enforces running verification commands and examining outputs before allowing success claims.

You need to run verification commands before claiming a release is ready because claiming work complete without verification leads to misinformation and rework. Evidence-first completion requires fresh outputs to guard against unchecked assumptions.