ship

Orchestrates a state-machine development pipeline from planning through PR review resolution.

1|Updated Mar 12, 2025
One-click install
npx skills add https://github.com/void2610/dotfiles --skill ship-void2610
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/void2610/dotfiles/tree/main/.claude/skills/ship
Command: npx skills add https://github.com/void2610/dotfiles --skill ship-void2610

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, gh, and includes scripts (resource) components.

What problem does it solve? Multi-phase development work (planning, branching, implementing, testing, committing, opening a PR, handling reviews) is easy to lose track of, especially across interrupted sessions. This Skill enforces a strict, resumable state machine so no phase is skipped, reordered, or forgotten. ## Core Features & Use Cases - State-Machine Pipeline: Drives 12 phases (plan, branch, impl, test, format, knowledge, commit, report, quiz, pr, review, fix) via ship.sh, with each phase transition verified by real postconditions (clean working tree, passing test command, open PR, zero unresolved review threads). - Checkpoints and Skips: Users can pause before any phase in natural language ("stop before every commit") or skip phases with a recorded reason, and resume interrupted flows from persisted state. - Branch Locking: After the branch phase completes, a guard hook blocks branch creation or switching until the flow finishes. - Use Case: Ask the AI to implement a feature; the Skill walks it through branch creation, implementation, running the repo's test/format commands, committing, opening a PR, waiting for the Copilot review and CI, and resolving review threads. ## Quick Start Start a new development flow by asking the AI to ship a feature, and it will initialize the pipeline with your goal and guide each phase through to PR review resolution.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I enforce a step-by-step development workflow with an AI coding assistant?▼

Use a state-machine pipeline that gates each phase behind verified postconditions. This Skill runs plan, branch, impl, test, format, commit, PR, and review phases through ship.sh, refusing to advance until checks like a clean working tree or passing tests actually pass.

How do I resume an interrupted development flow in a new session?▼

Run ship.sh status first; the pipeline state is persisted per branch in the git directory, so the flow resumes from the next pending phase. You never rely on the assistant's memory to determine current position.

Can I skip or pause specific phases like tests or commits?▼

Yes. Use ship.sh skip <phase> <reason> to bypass a phase with a recorded justification, or ship.sh checkpoint add <phase> to make the flow stop and wait for user approval before that phase begins.

Does this workflow work with any repository's test and format commands?▼

Yes, but each repository needs a .claude/ship.json file mapping test and format commands, such as {"test": "task test", "format": "task format"}. On first run the Skill infers commands from Taskfile, Makefile, or package.json and asks for approval.

Why can't I switch branches while the flow is running?▼

After the branch phase completes, the pipeline locks the branch until all phases finish, enforced by a guard hook that blocks git branch creation and switching. This prevents work from leaking across branches mid-flow.

What are the limitations of this development pipeline?▼

It delegates actual work to other skills (commit, pr-create, pr-review-fix) and only manages ordering and verification. The report and quiz gates only run on a specific host, and it requires bash, jq, git, and the GitHub CLI.