# /ship: Take a branch from finished code to an open PR

Source: https://trendhub.net/skills/garrytan-gstack/ship
Skill folder: https://github.com/garrytan/gstack/tree/main/ship
Pack: gstack (https://trendhub.net/skills/garrytan-gstack)
Works with: Claude Code, Claude Code (team mode for a shared repo), Codex, Cursor, OpenCode, Gemini CLI and other agents

Ship runs the release path for a feature branch in one command. It merges the base first, runs tests and coverage checks, reruns the review and an adversarial pass, bumps the version and changelog, audits docs, commits in bisectable chunks, verifies the frozen content again, then pushes and opens the PR. Routine choices are automatic; conflicts and risky findings stop for you.

## When to use it

- A feature is done and you want tests, review and release notes handled together.
- You want the version bump and changelog chosen consistently from the diff.
- You need a final check that nothing changed after tests and review passed.

## How it works

1. **Pre-flight and merge**: The agent refuses to ship from the base branch, fetches it and merges it in before any tests run.
2. **Test and review**: It runs the test suites, audits coverage and plan completion, then runs the pre-landing and adversarial reviews.
3. **Prepare the release**: It picks the version bump, updates CHANGELOG and TODOS, audits docs and commits in bisectable pieces.
4. **Verify frozen content**: No completion claim is allowed without fresh evidence; any later code change sends it back through tests and review.
5. **Push and publish**: It pushes the branch, opens or updates the PR and records ship metrics.

## What it steers the agent away from

- Claiming success without fresh verification evidence.
- Duplicate version bumps, pushes or PRs on reruns.
- Committing generated tests that fail.

## What it can touch

Runs git merges, tests and helper scripts, edits VERSION, CHANGELOG and docs, commits, pushes and opens a PR on your Git host.

## Pairs well with

- `/land-and-deploy`
- `/review`
- `/verify`

## Questions

### Does it ask before every step?

No. Routine work such as including uncommitted changes, small version bumps and changelog drafts proceeds without asking; complex conflicts and blocking findings stop for your answer.

### What happens if I change code after review?

The verification stage detects the change and routes back through tests and review before anything is pushed.
