verification-before-completion

Verification before completion requires running fresh verification commands and evaluating their outputs to validate success before marking work as complete. This evidence-based approach prevents premature completion claims in software development tasks.

Evidence-based status for code changes and pull requests means completion is only claimed after running fresh verification commands and interpreting their outputs to validate success. This gates completion status on verifiable test results rather than assumptions.

You prevent premature pull requests and deployments by gating completion status on fresh verification command outputs. This quality assurance mechanism requires reading and interpreting results to validate success before any work is marked complete.

This verification skill integrates with existing testing workflows by requiring fresh verification commands to be run and their outputs evaluated before completion. It complements code review processes by enforcing evidence-backed status claims for software development tasks.

Fresh verification commands are required because they produce current evidence of success. Relying on previous test results risks claiming completion based on outdated information, which can lead to premature PRs or deployments when code has changed since the last test run.

The skill applies specifically to software development tasks, code changes, tests, and pull requests. It requires fresh verification commands to be executable and their outputs readable, which may limit use in environments where command execution is restricted or outputs are inaccessible.