← ClaudeAtlas

ship-prlisted

Ship a single change through a worktree -> branch -> PR -> squash-merge -> cleanup workflow - pick the right branch type (feat/fix/chore/docs/hotfix), implement, verify with this repo's real build/typecheck/test commands, open the PR, check CI, merge, and clean up. Use for any single PR-sized change in any git repo with a GitHub remote - a bug fix, a small feature, a doc edit, a dependency bump. For 3+ independently shippable PRs from one analysis pass, see parallel-ship. For sequential phases where each PR builds on the last, see epic-ship.
davidtheproduct/claude-ship-skills · ★ 1 · AI & Automation · score 77
Install: claude install-skill davidtheproduct/claude-ship-skills
# Ship PR A repo-agnostic worktree -> branch -> PR -> squash-merge -> cleanup workflow. Works in any git repo with an `origin` remote and `gh` configured; the scripts detect the package manager and default branch rather than assuming pnpm/Turborepo/`main`. This is the atomic unit of the ship stack: `parallel-ship` and `epic-ship` both call this skill internally (per fanned-out agent and per phase respectively). Invoke it directly for anything that is one PR-sized change. > **Naming note:** if a repo you work in defines its own project-level `ship-pr` skill (tuned to that repo's quirks), rename this personal-level copy (e.g. `ship-pr-global`) - in Claude Code's skill resolution, a personal-level skill overrides a project-level one of the same name, so an identical name would silently shadow the tuned version. ## Step 1: Pick the branch type | Change scope | Prefix | | ---------------------------------------- | ---------- | | Docs only (markdown, `docs/**`) | `docs/` | | New behavior | `feat/` | | Bug correction (behavior existed, broke) | `fix/` | | Tooling/refactor, no behavior change | `chore/` | | Production is broken right now | `hotfix/` | If unsure between `feat/` and `fix/`: did this behavior exist and work correctly before? Correcting it is `fix/`. Adding something new is `feat/`. ## Step 2: Worktree -> implement -> verify -> ship -> merge -> cleanup 1. **Worktree**: