Ship Pipeline

VerifiedCaution

Ship pipeline — review a worktree change to convergence, then atomic commit, push, PR, address review, squash-merge, ff-only sync, cleanup.

Sby Skills Guide Bot
DevOpsAdvanced
7/22/2026
Claude Code
#git-workflow#pull-requests#code-review#worktree#release-automation

Recommended for

Automated summary

Drives a worktree change through the full ship lifecycle: a review loop to convergence, an atomic commit, push, PR creation, review follow-up, squash-merge, ff-only sync and cleanup.

Strengths

  • Runs ordered phases (isolate, review, commit, PR, address review, merge, sync) and stops only on the defined must-ask triggers
  • Enforces semantically atomic commits with a conventional subject under 72 characters and an Assisted-by trailer
  • Requires a converged review verdict on the latest pushed commit before merging, rather than a mechanics-only recheck
  • Handles worktree isolation plus post-squash-merge cleanup, including orphan branch removal

Limitations

  • Relies on five companion skills (smith-gh-pr, smith-git, smith-style, smith-worktree, smith-subagents) and Claude Code worktree/hook features
  • Assumes an authenticated gh CLI and a CodeRabbit review that actually ran, so it does not work outside that setup
  • Stacked PRs require the separate smith-stacks path and omitting --delete-branch, adding friction to the default flow
When to use it

Use it when a change in a worktree is ready and you want it delivered end-to-end through review, PR and merge with cleanup.

When not to use it

Avoid it for an urgent fix that needs no PR, or in a repository without gh and the required companion skills.

Security analysis

Caution
Quality score85/100

The skill orchestrates legitimate version-control and PR workflows using git and gh, including push, merge, and branch deletion. These are powerful, network-touching, and potentially destructive to remote branch state, so it warrants caution, but there is no exfiltration, obfuscation, or sabotage.

Findings
  • •Executes `git push` and `gh pr merge --squash --delete-branch`, which modify remote repository state and delete branches.
  • •Uses shell command substitution in live state (`git status -s`, `git branch --show-current`, `gh pr status`) though limited to declared git/gh tools.
How this analysis is made

Examples

Ship the current change
/smith-ship
Ship with an explicit PR scope
/smith-ship feat: add retry backoff to the webhook dispatcher
Ship end-to-end in plain language
Ship this worktree change end-to-end: run the review loop until it converges, make an atomic commit, open the PR, address the review findings, squash-merge, then sync the default branch and clean up the worktree.

name: smith-ship description: Ship pipeline — review a worktree change to convergence, then atomic commit, push, PR, address review, squash-merge, ff-only sync, cleanup. Invoke with /smith-ship when you want to ship the current change end-to-end. argument-hint: [scope or PR title] allowed-tools: Bash(git *), Bash(gh *)

/smith-ship — ship the current change end-to-end

Drive the change in the current worktree from review to merged, following smith conventions. Run phases in order; stop and surface only on the must-ask triggers in @smith-gh-pr/SKILL.md (Review Convergence Protocol). Argument (if given) is the intended PR scope/title.

Live state

  • Status: !git status -s
  • Branch: !git branch --show-current
  • Open PR (if any): !gh pr status 2>/dev/null | head -20

Procedure

Load and follow @smith-gh-pr/SKILL.md, @smith-git/SKILL.md, @smith-style/SKILL.md, @smith-worktree/SKILL.md, and @smith-subagents/SKILL.md.

  1. Isolate — check git status --porcelain FIRST: if the checkout is dirty, STOP and pick ONE path: (a) commit or stash the changes, then EnterWorktree; or (b) branch in place (git switch -c …) and continue in the current checkout — no EnterWorktree at all (the tree is still dirty and the worktree-dirty-guard hook would block it; a new worktree starts clean, stranding uncommitted changes). worktree.baseRef: head only preserves already-committed unpushed work, never uncommitted changes. Then, if on the EnterWorktree path in a background session, enter the worktree (see @smith-worktree) and rename the branch to the @smith-style convention before any push.
  2. Review to convergence — run the /smith-review loop; it owns the tool marshaling, per-round receipts, and convergence criteria. Do not ship until it reports converged.
  3. Commit — logically and semantically atomic; conventional subject ≤72, body ≤72/line, Assisted-by: trailer (see @smith-style). One concern per commit.
  4. Push & PR — push the renamed branch; gh pr create --base <default> --assignee @me with a What/Why/Testing body ending with the Assisted-by: line (@smith-style). Link issues only if real. The body and title are content: show them and create on an explicit yes (@smith-guidance Harmless).
  5. Address review — follow @smith-gh-pr (Code Review Cycle, Posting Review Findings) for fetching, replying, attribution, suggestion blocks, and the content-vs-mechanics gate. Ship-specific: fix high-confidence findings with fix + amend (not new commits); after each push rerun the /smith-review loop to a fresh converged verdict (full receipt + criteria — a mechanics-only recheck is not convergence); confirm CodeRabbit actually ran before trusting 0 (@smith-gh-pr "CodeRabbit fails OPEN").
  6. Merge — on a converged verdict for the LATEST pushed commit (earlier convergence does not carry across new commits), gh pr merge --squash --delete-branch (targets the current branch's PR). If this branch has an open child PR stacked on it, OMIT --delete-branch and follow @smith-stacks instead.
  7. Sync & clean up — ExitWorktree (remove), then ff-only pull the repo's DEFAULT branch in the primary checkout; clear any squash-merge orphan branch (@smith-worktree Sync-After-Squash-Merge).

State results in your own message (in-band); end with a result: line.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/ship-pipeline-mrwakbjb/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/ship-pipeline-mrwakbjb' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/ship-pipeline-mrwakbjb/download' --output '.skill-downloads/ship-pipeline-mrwakbjb/SKILL.md.part' && mv '.skill-downloads/ship-pipeline-mrwakbjb/SKILL.md.part' '.skill-downloads/ship-pipeline-mrwakbjb/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Bash(git *), Bash(gh *)

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/ship-pipeline-mrwakbjb/SKILL.md' && test -s '.skill-downloads/ship-pipeline-mrwakbjb/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/smith-ship' && cp -R '.skill-downloads/ship-pipeline-mrwakbjb' '.claude/skills/smith-ship'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/ship-pipeline-mrwakbjb'

openskills read 'ship-pipeline-mrwakbjb'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/ship-pipeline-mrwakbjb/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills