Stats
Actions
Tags
From ship
Executes Ship's end-to-end production workflow from raw requirement to PR: design, dev, E2E, review, QA, refactor, handoff. Intended for explicit /ship:auto or full pipeline requests.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ship:autoThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Full staged workflow for explicit end-to-end production delivery.
Full staged workflow for explicit end-to-end production delivery.
Resolve ../../scripts/auto-orchestrate.sh relative to this skill file, then
run the shared stage-aware orchestrator:
SHIP_ORCH="../../scripts/auto-orchestrate.sh"
if [ -f .ship/ship-auto.local.md ]; then
"$SHIP_ORCH" resume
else
"$SHIP_ORCH" init '<user requirement goes here>'
fi
Then follow the /ship:auto dispatch loop: read PROMPT_FILE, dispatch the
agent, classify the report card, and call complete <PHASE>.
/ship:auto is only for full production workflow runs. If the user asks for a
specific phase such as design, development, E2E, review, QA, refactor, or
handoff, invoke that standalone /ship:* skill directly instead of routing
through auto.
npx claudepluginhub heliohq/ship --plugin shipRoutes ambiguous software-delivery requests to the smallest useful Ship workflow: a single skill, a phase bundle, or the full /ship:auto pipeline. Use when a user says build/check/ship without a phase.
Autonomous end-to-end development from requirement to delivery. Use when user wants complete automation, 'build X for me', or full feature implementation without manual steps.
Chains plan → build → test → review → ship into a structured feature lifecycle. Use when starting a new feature or project iteration and want a full pipeline from idea to deployment.