ship

Drives a change from implementation through scoped gates, PR merge, and live-artifact verification.

Updated May 31, 2026

Search Tags:#git #pull request #github #release workflow #deployment verification #merge automation #ci gates

One-click install

npx skills add https://github.com/4444J99/limen --skill ship-4444j99

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/4444J99/limen/tree/main/.claude/skills/ship
Command: npx skills add https://github.com/4444J99/limen --skill ship-4444j99

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Shipping a change often stalls between implementation and merge, or gets declared done when the PR merges even though the live artifact never changed. This Skill enforces a single end-to-end path — branch, scoped gates, PR, policy-checked merge, live verification, closeout — so a change is only called shipped when it is proven live. ## Core Features & Use Cases - Scoped gating: Runs `scripts/verify-scoped.sh` so only the gates implicated by the diff execute, with every skipped gate named. - Predicate-based merge: Uses `scripts/merge-policy.sh` and `scripts/await-pr.sh` to merge only when required checks clear, with explicit CLEARED/HOLD/BLOCKED handling and no hand-rolled polling. - Live-artifact proof: Verifies the deployed surface via `scripts/ship-gate.py` or surface-specific probes, treating merged-but-not-live as not shipped. - Use Case: After implementing a fix on a topic branch, invoke the skill to gate the diff, open and merge the PR on green required checks, confirm the deployed URL reflects the change, and produce a closeout relay with predicate verdicts. ## Quick Start Ask the agent to ship the current change end-to-end using the ship skill, from scoped verification through merge and live-artifact proof.

Frequently Asked Questions about ship

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

When should I use ship-docs.sh instead of the full ship workflow?▼

Use scripts/ship-docs.sh for a one-file documentation append; it compresses the gate, PR, and merge steps into a single command. Code or product-facing changes still follow the full six-step workflow.