# Ship

> Ship completed work through the repo's actual delivery flow: checkpoint, commit, push, PR, and release steps. Reads project-specific delivery commands from config.

- Skill: `garyld1962/ship-4` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add garyld1962/ship-4`
- Raw SKILL.md: https://api.skillmd.com/api/skills/garyld1962/ship-4/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: garyld1962 (https://skillmd.com/u/garyld1962)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/garyld1962/ship-4

---


# /ship — Deliver Completed Work

**Purpose:** Move completed work through the repo's actual delivery flow. Runs checkpoint, creates a clean commit, pushes, creates a PR, and optionally runs release steps — all using the project's configured commands.

## When to Use

- Repo has a configured delivery flow (`ship.config.md` or `CLAUDE.md` Ship section)
- Work needs project-specific release steps beyond a standard PR
- You want a single command from completion through release

## When NOT to Use

- No ship config exists — use `/pr` for the standard PR flow
- You only need the quality gate — use `/checkpoint`
- Work is mid-implementation — finish first

## Pre-flight Required Config

Before proceeding, verify:

1. Check `<project>/.claude/ship.config.md` exists, OR check that `<project>/CLAUDE.md` has a `## Ship` or `## Delivery` section with build/test/ship commands.

   If neither exists, halt:
   > This skill needs delivery commands for your project.
   >
   > Set up interactively:
   > ```
   > /configure ship
   > ```
   >
   > Or copy the template and edit:
   > ```
   > cp claude/ship/config.template.md <project>/.claude/ship.config.md
   > ```

2. Verify `build_command`, `test_command`, and `ship_command` are present and non-placeholder.

3. If healthy, proceed silently.

## Arguments

- (no argument) — run the full delivery flow
- `--skip-checkpoint` — skip lint/build/test gate (use with care)
- `--draft` — create a draft PR instead of a ready PR

## Rubrics

This skill references:
- `_internal/repo-delivery` — ship contract and guardrails

## Workflow

### Step 1: Confirm State

- Check current branch, staged changes, and working tree
- Verify we're not on the default branch (main/master)
- Show what will be shipped: files changed, commit count

### Step 2: Checkpoint

Unless `--skip-checkpoint`:
- Run the project's build command
- Run the project's test command
- Run lint if configured
- Report PASS/FAIL per check
- Halt on failure — do not ship broken code

### Step 2.5: Security Quick Check (when warranted)

If the diff touches authentication, authorization, input handling, rendering of user content, or persistence, apply the **security-quick-check** rubric (`_internal/security-quick-check/SKILL.md`).

Skip when the diff is purely cosmetic or has no trust-boundary involvement. Halt on findings; do not ship until resolved.

### Step 3: Commit

- Create a clean commit with a message that reflects the actual changes
- Follow the project's commit conventions if defined in CLAUDE.md

### Step 4: Push

- Push to the remote with upstream tracking
- Report the remote branch name

### Step 5: Create PR

- Create a PR with a summary based on the commit(s)
- Use `--draft` if requested
- Report the PR URL

### Step 6: Release Steps (Optional)

If the project config defines `tag_command`, `release_command`, or `deploy_command`, offer to run them:
> "Project has release steps configured. Run them? (tag / release / deploy)"

Only run with user confirmation.

## CRITICAL: Do Not Guess

- Do NOT assume the package manager, branch name, or script names. Read from config.
- Do NOT auto-ship unrelated changes.
- Do NOT claim success without build/test passing.
- Do NOT run release steps without user confirmation.
- Do NOT push to main/master without explicit user instruction.