shipyard

Shipyard

Cross-platform CI for AI agents. Validates the exact commit on every machine you configure — local Mac, SSH-reachable VMs, cloud runners — and merges only when everything is green.

curl -fsSL https://generouscorp.com/Shipyard/install.sh | sh
cd my-project
shipyard init              # detects your project, probes your machines
shipyard run               # validates on every platform you configured
shipyard ship              # validate, open PR, merge on green
shipyard watch             # live-tail an in-flight ship
shipyard wait pr 151 --state green  # wait on release / PR / run conditions
shipyard auto-merge <pr>   # cron-friendly one-shot merge-on-green
shipyard rescue <pr>       # cancel + redispatch every stuck queued run on a PR
shipyard runner watch --kill-hung-workers  # daemon-mode prevent + auto-kill hung Workers
shipyard update            # self-update the CLI (or `--check` to peek)
shipyard doctor --rate-limit  # inspect REST + GraphQL buckets separately
shipyard release-bot setup # guided RELEASE_BOT_TOKEN setup
shipyard cloud retarget    # switch one target's runner mid-flight
shipyard cloud add-lane    # append a new lane to an in-flight PR
shipyard changelog init    # opt in to post-release CHANGELOG auto-sync

Highlights

• Designed for AI agents. Claude Code and Codex one-command setup; agents validate and merge without you handing them notarization keys or publishing accounts.
• Evidence-based merge gate. shipyard ship refuses to merge unless every required platform has passing evidence for the exact HEAD SHA — not the most-recent run, not the branch tip, the SHA.
• Parallel-agent-aware queue. Multiple agents in multiple worktrees share one machine-global queue with priorities, FIFO scheduling, and automatic deduplication.
• Declarative security & governance. One TOML line picks a profile (solo or multi); one CLI command makes GitHub branch protection, tag protection, and workflow token permissions match.
• 22 ecosystem detectors. shipyard init recognises CMake, Swift, Xcode, Rust, Go, Node (pnpm/bun/yarn/npm), Python (uv/poetry/pip), Gradle, Maven, .NET, Flutter, Dart, Deno, Ruby, Elixir, PHP.
• Self-hosted runner watchdog. shipyard runner status / cleanup --fix / watch --fix / watch --kill-hung-workers detect and auto-recover the stuck-runner failure mode (orphaned busy state, hung worker, stale queued runs). runner kill --pid <pid> is the explicit one-shot equivalent. See docs/runner-watchdog.md.
• One-shot PR rescue. shipyard rescue <pr> cancels and redispatches every stuck queued workflow run on a PR onto github-hosted (or any provider via --to). --rerun-failed also re-arms watchdog-cancelled runs; --all-stuck is the repo-wide variant. Pairs with the watchdog to form a complete prevent → recover toolkit.
• In-tool self-update. shipyard update is the discoverable upgrade path (no more curl-pipe to remember); --check reports installed-vs-available, --to v0.55.0 pins a specific tag for rollback.
• Graceful GraphQL rate-limit degradation. shipyard auto-merge and shipyard wait pr fall back to REST automatically when GraphQL exhausts (separate 5000/hr bucket). shipyard doctor --rate-limit shows both buckets so you can see which one is hot.
• Optional tartci VM integration. Projects with Apple Silicon VM fleets can keep local VM images, caches, and per-host capacity in tartci, then let Shipyard resolve the active profile into one concrete GitHub runner selector before each dispatch.
• Agent-readable runner metrics. shipyard metrics records local command timings, imports GitHub Actions jobs, and imports optional tartci VM timing exports into a small SQLite store. Agents can ask for summaries, drift findings, and placement advice without requiring tartci or any observability service.

Installation

Claude Code (recommended)

Two commands to register the marketplace and install the plugin:

claude plugin marketplace add danielraffel/Shipyard
claude plugin install shipyard

Then set up your project:

/shipyard:init

The plugin uses the CLI under the hood. On first session start it auto-installs the binary if it can't find shipyard on PATH — and skips the install if it can. If you've already installed the CLI (via install.sh or a project pinner like pulp's tools/install-shipyard.sh), make sure its bin directory is on PATH before you install the plugin; that way the plugin respects your existing pin instead of installing its own copy alongside it.

Plugin + CLI are independently versioned; the plugin's version covers slash commands / skills / hooks, while the CLI's version covers the binary. It's safe to have both.

Codex / CLI