ship

Execute a planned task into a reviewed pull request with isolated workers and immutable CI coverage.

1|1|Updated Jul 23, 2026
One-click install
npx skills add https://github.com/nearmap/shipyard --skill ship-nearmap
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/nearmap/shipyard/tree/main/skills/ship
Command: npx skills add https://github.com/nearmap/shipyard --skill ship-nearmap

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning an approved plan into a mergeable pull request involves coordinating branching, implementation, CI, independent review, and record-keeping; this Skill orchestrates that entire delivery loop so the PR head, the CI-green commit, and the reviewed commit are always the same commit before anything merges. ## Core Features & Use Cases - Phased worker orchestration: Dispatches disposable START, BUILD, and GATE subagents with idempotent, slice-granular checkpoints so interrupted runs resume without redoing committed work. - Immutable independent review: Pins review to exact base/head SHAs in an isolated worktree, runs an adversarial gate at a frontier-tier model, and resets review scope whenever a fix is pushed. - Durable accounting: Posts retrospectives, standalone token-usage and ship-metrics JSON logs, and optional scanned transcript attachments to the issue tracker, and merges only after explicit user authorization. - Use Case: After planning a roadmap with /sy:plan and speccing a task with /sy:spec, run the ship skill on the task to get a draft PR built to the plan, reviewed by an independent gate, with CI green and a full paper trail on the ticket. ## Quick Start Run the ship skill with the task key, for example: ship TASK-123, to execute the planned task through build, review, and handoff to a merge-ready pull request.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I turn a planned task into a pull request with Claude Code?▼

Run the ship skill with the task key after the task has an execution plan posted by /sy:spec. It dispatches START, BUILD, and GATE workers that branch, implement the plan, open a draft PR, and drive CI and independent review to convergence.

How does the independent code review gate work?▼

The gate reviews an isolated worktree pinned to exact base and head SHAs at a frontier-tier model with max effort. Every suspected bug must survive a refutation attempt, and any fix push resets the review scope so the reviewed commit always equals the PR head.

Does the ship skill merge pull requests automatically?▼

No, it never merges automatically. The run stops at handoff with the PR ready, and merge happens only after explicit user authorization, followed by revalidation of CI and review coverage against the verified head.

What happens if a ship run is interrupted mid-task?▼

Checkpoints are slice-granular and idempotent, recorded in a ship-state.yaml file. On resume the parent reconciles recorded state against git and PR ground truth, then re-dispatches the correct phase without redoing committed or pushed work.

What are the limitations of the ship skill?▼

It requires a task with a current execution plan comment; without one it stops and returns to /sy:spec. It also depends on a configured tracker (Jira or GitHub Projects), and material drift from the plan base sends the task back for re-speccing.