ship-release

To block a CI/CD pipeline from shipping code with a low review score, use a release gating mechanism that checks for a non-negotiable score threshold. This Skill halts deployment unless the review score is 8 or higher and all required pipeline artifacts are validated.

Release gating in continuous delivery is a safeguard that validates required pipeline outputs before allowing deployment. It verifies the presence of spec, plan, build session, and test result files, explicitly failing the release if any required artifact is missing or incomplete.

To generate an auditable rollback command and ship-log for a failed release gate, the release process emits a structured JSON payload upon failure. This output includes a deterministic rollback reference for git reverts and metadata for updating the Linear ticket.

Yes, you can automatically update a Linear ticket to Done after passing tests and pipeline validation. The release process verifies test-results.json and build completion, then updates the ticket status to Done and appends a ship pattern entry to lessons.jsonl upon success.

No, release gating does not work without checking for open blockers in the plan. A core validation requirement ensures the plan.md file contains no open blockers before shipping, failing the pipeline gate if any unresolved blockers are detected.

When a continuous delivery pipeline fails the review score threshold, the process stops shipping and outputs an explicit gate failure JSON. This structured failure payload provides the necessary audit trail and prevents the deployment from proceeding.