verification-before-completion

To gate pull request completion, this skill executes your full verification workflow, parses test and build outputs, validates exit codes, and blocks success announcements until evidence meets predefined thresholds.

Evidence-based verification is a gating process that requires running tests, builds, and linters to produce fresh results before any completion claims are accepted for code commits or release gates.

You prevent premature success statements in CI pipelines by enforcing a verification gate that parses outputs and validates exit codes, ensuring completion claims are backed by fresh verification evidence.

Yes, you can integrate this verification gate into pull requests, releases, and task handoffs to provide a repeatable process for running, validating, and reporting verification outputs before acceptance.

You validate exit codes and test outputs by executing the full verification command suite, parsing the results, and gating success announcements only when the fresh verification evidence meets predefined thresholds.

The verification gate requires executing the full verification workflow and relies on predefined thresholds, meaning completion claims cannot be accepted if fresh test, build, or linter evidence is unavailable or fails validation.