spec-ship

Ship It

Push your work to GitHub and open a pull request — handling prerequisites, branch creation, pushing, and PR generation automatically.

This skill complements spec-checkpoint. Use spec-checkpoint to commit locally (with quality gates), then spec-ship to get the code to GitHub for review.

Instructions

Step 0: Prerequisites

Verify tooling before doing anything else.

1. GitHub CLI installed?

   gh --version
   

   If the command fails (not found):

   • Detect the platform and attempt to install:
     • Windows: winget install --id GitHub.cli
     • macOS: brew install gh
     • Linux (Debian/Ubuntu): follow the official apt instructions
   • If auto-install fails, tell the user what to install and stop.

2. GitHub CLI authenticated?

   gh auth status
   

   If not authenticated, tell the user:

   GitHub CLI is not logged in. Please run this in the prompt:
     ! gh auth login
   Then re-run /spec-ship.
   

   Stop here — do not proceed until auth is confirmed.

3. Git remote exists?

   git remote -v
   

   If no remote named origin exists, stop and tell the user:

   No git remote found. Add one with:
     git remote add origin https://github.com/{user}/{repo}.git
   

Step 1: Detect the Environment

Run these commands to understand the current state:

1. git branch --show-current — get the current branch name
2. Detect the default branch:

   gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name'
   

3. git status --porcelain — check for uncommitted changes

If there are uncommitted changes, stop and tell the user:

You have uncommitted changes. Run /spec-checkpoint first to commit them, then /spec-ship to push.

Store the default branch name for use throughout the remaining steps.

Step 2: Check for Unpushed Commits

Determine if there are commits that haven't been pushed yet.

If on a feature branch with a remote tracking branch:

git log @{upstream}..HEAD --oneline