Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
Execute an approved split plan, shipping each change group separately as its own branch and PR or as sequential commits on the current branch.
Install Split And Ship
$ npx skills add tobihagemann/turbo --skill split-and-ship -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install tobihagemann/turbo split-and-ship --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .claude/skills && cp -r skills-src/codex/skills/split-and-ship .claude/skills/split-and-ship && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "split-and-ship" agent skill from https://github.com/tobihagemann/turbo/tree/main/codex/skills/split-and-ship into .claude/skills/split-and-ship/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "split-and-ship", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/tobihagemann/turbo/tree/main/codex/skills/split-and-shipType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add tobihagemann/turbo --skill split-and-ship -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install tobihagemann/turbo split-and-ship --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .agents/skills && cp -r skills-src/codex/skills/split-and-ship .agents/skills/split-and-ship && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "split-and-ship" agent skill from https://github.com/tobihagemann/turbo/tree/main/codex/skills/split-and-ship into .agents/skills/split-and-ship/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "split-and-ship", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add tobihagemann/turbo --skill split-and-ship -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install tobihagemann/turbo split-and-ship --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/codex/skills/split-and-ship .cursor/skills/split-and-ship && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "split-and-ship" agent skill from https://github.com/tobihagemann/turbo/tree/main/codex/skills/split-and-ship into .cursor/skills/split-and-ship/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "split-and-ship", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/tobihagemann/turbo.git --path codex/skills/split-and-ship--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add tobihagemann/turbo --skill split-and-ship -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install tobihagemann/turbo split-and-ship --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/codex/skills/split-and-ship .gemini/skills/split-and-ship && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "split-and-ship" agent skill from https://github.com/tobihagemann/turbo/tree/main/codex/skills/split-and-ship into .gemini/skills/split-and-ship/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "split-and-ship", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install tobihagemann/turbo split-and-shipInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add tobihagemann/turbo --skill split-and-ship -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .github/skills && cp -r skills-src/codex/skills/split-and-ship .github/skills/split-and-ship && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "split-and-ship" agent skill from https://github.com/tobihagemann/turbo/tree/main/codex/skills/split-and-ship into .github/skills/split-and-ship/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "split-and-ship", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add tobihagemann/turbo --skill split-and-ship -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install tobihagemann/turbo split-and-ship --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/codex/skills/split-and-ship .opencode/skills/split-and-ship && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "split-and-ship" agent skill from https://github.com/tobihagemann/turbo/tree/main/codex/skills/split-and-ship into .opencode/skills/split-and-ship/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "split-and-ship", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
split-and-ship- GitHub stars
- 409
- Token cost
- ~1.9k tokens
- SKILL.md length
- 1,116 words
- Files
- 1
- Skills in repo
- 81
- Repo updated
- First seen
- Licence
- MIT
At a glance
Execute an approved split plan, shipping each change group separately as its own branch and PR or as sequential commits on the current branch.
- Works in 3 steps: Choose Realization Path → Ship as Separate Branches and PRs → Ship as Commits on the Current Branch
- The user asks to split and ship
- SKILL.md covers Context, Task Tracking, Step 1: Choose Realization Path and Step 2: Ship as Separate…, plus 2 more sections
- Calls git and gh
What it does
Split And Ship is an agent skill from tobihagemann/turbo. Execute an approved split plan, shipping each change group separately as its own branch and PR or as sequential commits on the current branch. Use when the user asks to "split and ship", "ship the split plan", "create separate PRs", or "split changes into branches".
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development. It works with Git. The repository describes itself as: Reusable workflows for planning, building, reviewing, and shipping with Claude Code and Codex. The licence is MIT.
When your agent uses it
- The user asks to split and ship
- Ship the split plan
- Create separate PRs
- Split changes into branches
Example prompts
- “split and ship”
- “ship the split plan”
- “create separate PRs”
- “/split-and-ship”
Workflow steps
3 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 160a0fa. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gitgh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Split And Ship loads about 1.9k tokens when it runs. Until then it costs about 70 tokens; SKILL.md has 1,116 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from tobihagemann/turbo at commit 160a0fa, republished under its MIT licence (© tobihagemann). 1,116 words, ~1,871 tokens.
Download SKILL.mdSave it as
.claude/skills/split-and-ship/SKILL.md (or your agent's skills folder).- name
- split-and-ship
- description
- Execute an approved split plan, shipping each change group separately as its own branch and PR or as sequential commits on the current branch. Use when the user asks to "split and ship", "ship the split plan", "create separate PRs", or "split changes into branches".
Split and Ship
Ship an approved split plan so each change group becomes its own reviewable unit, either as a separate branch and PR or as a sequential commit on the current branch.
Context
A split plan must exist in the conversation. The plan specifies an ordered list of groups, each with a name, file list, and any dependencies on earlier groups.
Task Tracking
At the start, use update_plan to track each phase, restating any remaining steps of a parent workflow alongside them:
- Choose realization path
- Ship the groups
- Summarize
Step 1: Choose Realization Path
Detect the repository state:
- Default branch:
gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name' - Current branch name, and whether it tracks an upstream
- Whether a PR already exists for the current branch (
gh pr view)
Sample the prevailing workflow from recent default-branch history (git log --first-parent origin/<default-branch> -n 30 --pretty=%s): judge whether changes mostly land through pull requests (merge-PR commits or (#N)-suffixed squash commits) or are committed directly to the default branch.
Output a one-line summary of the detected state as text. Then use request_user_input to choose how to ship the groups:
- Separate branches and PRs — one branch and PR per group (Step 2)
- Commit each group and push — one commit per group on the current branch, then push (Step 3)
- Commit each group only — one commit per group on the current branch, no push (Step 3)
Recommend the option that fits this repo by listing it first and labeling it (Recommended): a PR-based history recommends separate branches and PRs; a direct-commit history recommends committing each group on the current branch.
If the user declines (chooses the free-form "Other" option or asks to abort), leave the changes staged and do not commit.
Step 2: Ship as Separate Branches and PRs
Take this step only when the user chose separate branches and PRs.
Prepare the working tree
Stash all changes including untracked files (git stash --include-untracked) without unstaging first.
Verify git stash list shows the saved changes and git status --short lists nothing the stash should have taken before proceeding. Entries for a submodule, a nested repository, or files a stashed ignore rule had hidden may remain. When either check fails, stop and report where the changes now are.
Ship each group
Use update_plan to track each group, restating any remaining steps of a parent workflow alongside them. Process groups in order.
For each group:
- Determine branch: If the current branch already has a PR and this group's changes align with the PR's purpose, stay on the current branch. Otherwise, use
request_user_inputto confirm the proposed branch name and create it from the appropriate base:- Group that builds on an earlier group: branch from that group's branch (stacked)
- Group with no dependencies: branch from the default branch (independent)
- Restore and stage this group's files from the stash's staged snapshot (
git checkout 'stash^2' -- <files>restores and stages in one operation). For files with hunks belonging to different groups, restore the file, useapply_patchto remove the unwanted hunks, then re-stage it (git add <file>): for an independent group, remove every other group's hunks; for a stacked group, remove only later groups' hunks (earlier groups' hunks are already in its base). After committing, reset the working tree (git checkout -- .) to clean up before the next group. - Commit and push: run the
$commit-rulesskill to load commit message rules, commit the staged changes following them, thengit push - Create or update PR:
- Staying on existing branch with a PR: run the
$update-prskill - New branch: run the
$create-prskill targeting the appropriate base (default branch for independent groups, previous group's branch for stacked groups)
- Staying on existing branch with a PR: run the
Clean up and summarize
- Drop the stash
- Check out the last created branch
- Output a summary table: group name, branch, PR URL, and base branch. For a group whose PR was not posted, print the handed-over body file path in place of the URL.
Then call update_plan to mark this step completed and continue with the next step of the active workflow.
Show full SKILL.md (440 more words)Show less
Step 3: Ship as Commits on the Current Branch
Take this step only when the user chose to commit each group. This path stays on the current branch and creates no branches or PRs.
Prepare the working tree
Stash all changes including untracked files (git stash --include-untracked) without unstaging first.
Verify git stash list shows the saved changes and git status --short lists nothing the stash should have taken before proceeding. Entries for a submodule, a nested repository, or files a stashed ignore rule had hidden may remain. When either check fails, stop and report where the changes now are.
Commit each group
Run the $commit-rules skill to load commit message rules. Use update_plan to track each group, restating any remaining steps of a parent workflow alongside them. Process groups in order.
For each group:
- Restore and stage this group's files from the stash's staged snapshot (
git checkout 'stash^2' -- <files>restores and stages in one operation). For files with hunks belonging to different groups, restore the file, useapply_patchto remove the hunks that belong to later groups, then re-stage it (git add <file>). - Commit the staged changes with a message following the loaded rules. If a commit hook modifies files, re-stage them before retrying.
- Reset the working tree (
git checkout -- .) to clean up before the next group.
Push and summarize
- If the chosen option includes pushing, push the current branch's remote (
git push) - Drop the stash
- Output a summary table: group name and commit subject
Then call update_plan to mark this step completed and continue with the next step of the active workflow.
Rules
- Run the
$commit-rulesskill before every commit; do not commit without loading it first. - Never lose uncommitted work. Both paths stash all changes before shipping. Before dropping the stash, restore and report every stashed change that no group shipped, rather than discarding it: re-apply the unstaged changes with
git diff 'stash^2' stash | git apply --3way --allow-empty, restore untracked files withgit checkout 'stash^3' -- <files>, then unstage everything withgit reset -q. Report any hunk that does not apply. If any step fails (commit hook, push, PR creation), stop and report the failure, which groups have been shipped, and that the stash still contains all changes for recovery. A group whose PR was handed over for editing rather than posted is not a failure; record it in the summary and continue. - For stacked groups, the PR description should note the dependency chain.
- Don't reference
.turbo/content (filenames, acceptance criteria, step numbers, headings) in branch names..turbo/is gitignored, so these references would be opaque to anyone reading without local copies.
© tobihagemann, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in codex/skills/split-and-ship of tobihagemann/turbo.
Open the folder on GitHubat commit 160a0fa
Compare with similar skills
Split And Ship next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Split And Ship this skilltobihagemann/turbo | 409 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 297k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 5 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Code Design Rationale Investigatorcursor/plugins | 10k | 9 repos | ~2.6k | Automated safety check: Pass | None | |
| Contributor-First PR MergeHKUDS/OpenHarness | 16k | 1 repos | ~847 | Automated safety check: Pass | MIT | |
| Finishing A Development Branchfarm-fe/farm | 5.6k | 34 repos | ~1.8k | Automated safety check: Pass | MIT |
Similar skills
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
- Official
Code Design Rationale Investigator
cursor/plugins
Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.
Contributor-First PR Merge
HKUDS/OpenHarness
Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.
Finishing A Development Branch
farm-fe/farm
A skill your agent uses when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for…
Migrate Internal Package into Ghost
TryGhost/Ghost
Moves a package from another TryGhost repository into Ghost as an internal workspace package while keeping its Git history, with checkpoints for the steps that need an administrator.
More from tobihagemann/turbo
All 81 skills in this repoConsult Oracle
tobihagemann/turbo
Consult ChatGPT Pro via ChatGPT browser automation for problems that resist standard approaches.
Fetch PR Comments
tobihagemann/turbo
Fetch and summarize review feedback and conversation from a GitHub PR (unresolved review threads, review bodies, and PR conversation comments) without making changes.
Recall Rationale
tobihagemann/turbo
Recall why a past change was made by locating the Claude Code transcript that produced it.
Resolve PR Comments
tobihagemann/turbo
Evaluate, fix, answer, and reply to GitHub pull request review comments and conversation comments.
Resolve PR Comments
tobihagemann/turbo
Evaluate, fix, answer, and reply to GitHub pull request review comments and conversation comments.
Assess Technical Debt
tobihagemann/turbo
Assess project-wide structural technical debt: complexity hotspots, deprecated API usage, duplication clusters, architecture rot, and low-value tests.
Related
Works with
Categories
Questions about Split And Ship
What does Split And Ship do?
Execute an approved split plan, shipping each change group separately as its own branch and PR or as sequential commits on the current branch. Split And Ship is an agent skill from tobihagemann/turbo. Execute an approved split plan, shipping each change group separately as its own branch and PR or as sequential commits on the current branch.
When should I use Split And Ship?
Split And Ship fits situations like: the user asks to split and ship; ship the split plan; create separate PRs; split changes into branches.
How do I install Split And Ship in Claude Code?
Run `npx skills add tobihagemann/turbo --skill split-and-ship -a claude-code`. Or copy the skill folder (codex/skills/split-and-ship in tobihagemann/turbo) into .claude/skills/split-and-ship in your project. Claude Code loads it when a task matches its description.
How do I install Split And Ship in Codex?
Run `npx skills add tobihagemann/turbo --skill split-and-ship -a codex`. Or copy the skill folder (codex/skills/split-and-ship in tobihagemann/turbo) into .agents/skills/split-and-ship in your project. Codex loads it when a task matches its description.
Can I use Split And Ship in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add tobihagemann/turbo --skill split-and-ship -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/split-and-ship, .gemini/skills/split-and-ship, .github/skills/split-and-ship and .opencode/skills/split-and-ship in your project.
What does Split And Ship need to run?
Going by SKILL.md and its folder, Split And Ship needs the command-line tools its instructions call (git and gh).
Does Split And Ship access the network?
SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Split And Ship safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Split And Ship use?
Split And Ship is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Split And Ship use?
About 1.9k tokens (SKILL.md is roughly 7.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Split And Ship?
Skills that share tags, products or a category with Split And Ship: Finishing a Development Branch (obra/superpowers, 297k stars), Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars), Code Design Rationale Investigator (cursor/plugins, 10k stars) and Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Split And Ship?
tobihagemann (a GitHub user) maintains it in tobihagemann/turbo, which has 409 GitHub stars. The repository holds 81 skills in this directory. The repository was last updated on October 9, 2026.
Source: tobihagemann/turbo on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.