/ship and /finalize-pr

One command. Commit, push, open the PR, fix CodeQL, resolve threads, fix CI, verify everything is green. Never merges. That’s a human decision.

/ship is the local escape hatch for the cloud pipeline. The cloud pipeline (ai-workflows, claude-code-routines) gets a PR opened and reviewed without you. /ship is what you run from a Claude Code session when you are the one iterating on a PR. It drives that PR to a ready-to-merge state in one command.

What `/ship` does

/ship is a thin orchestrator. It detects uncommitted changes (commits them), discovers recently created PRs, then for each PR invokes /finalize-pr, which is where the real work happens.

/ship
  ├─ Step 0: verify git repo
  ├─ Step 1: commit any uncommitted changes; discover PRs in scope
  ├─ Step 1.5: build a context brief from the conversation
  ├─ Step 2: invoke /finalize-pr per PR, sequentially
  └─ Step 3: re-verify each PR with live GitHub state before reporting

What `/finalize-pr` does

/finalize-pr is the loop. Five phases per PR:

Phase	What it owns
1. Discover	Resolve which PR or PRs to act on (current branch, all, or org-wide)
2. Resolve loop	Start CI monitor in background; in parallel: invoke `/resolve-codeql fix`, `/resolve-pr-threads`, merge-conflict resolution; once CI completes, run `/simplify` once on the cumulative changes
3. Verify gate	Re-query live GitHub state: `state`, `mergeable`, `mergeStateStatus`, `reviewDecision`, `statusCheckRollup.state`, all `reviewThreads.isResolved`, CodeQL alert count
4. Update metadata	A subagent updates PR title, description, linked issues
5. Report ready	Emit the canonical PR status block; wait for human merge

What it never does

Never merges. Merge is always a human decision.
Never approves. No auto-approval of PRs.
Never crosses org boundaries in org-wide mode.
Never bypasses branch protection.

Subagents in the call chain

/ship → /finalize-pr → /resolve-codeql fix
                     → /resolve-pr-threads → superpowers:receiving-code-review
                     → /simplify
                     → haiku subagent (PR metadata update)
                     → background CI monitor (Task tool)

Each subagent runs scoped to its task and reports back. The orchestrator re-verifies live state. It never trusts a subagent’s self-report as ground truth.

When to use `/ship` vs the cloud pipeline

Situation	Use
Issue is filed, you want a PR drafted without thinking	`ai-workflows` (the cloud pipeline triggered on issue open)
You’re editing a PR locally and want CI/threads/CodeQL handled in one command	`/ship` from your Claude Code session
You want a daily org-wide sweep	`claude-code-routines` (cron-scheduled)
You want to know if a PR is really ready to merge	`/finalize-pr <N>` directly: gives you the canonical gate output without re-running fixes

Where to go next

CodeQL resolution

Why CodeQL is fixed separately from CI checks, and what /resolve-codeql does.

claude-code-plugins

The plugin home for /ship, /finalize-pr, and all the supporting skills.

Source: ship/SKILL.md

The full skill definition.

Source: finalize-pr/SKILL.md

Phases, gates, and the merge prohibition.

AI development

Autonomous agents

Agent ops

Local LLM

What `/ship` does

What `/finalize-pr` does

What it never does

Subagents in the call chain

When to use `/ship` vs the cloud pipeline

Where to go next

CodeQL resolution

claude-code-plugins

Source: ship/SKILL.md

Source: finalize-pr/SKILL.md

​What /ship does

​What /finalize-pr does

​What it never does

​Subagents in the call chain

​When to use /ship vs the cloud pipeline

​Where to go next

CodeQL resolution

claude-code-plugins

Source: ship/SKILL.md

Source: finalize-pr/SKILL.md

What `/ship` does

What `/finalize-pr` does

What it never does

Subagents in the call chain

When to use `/ship` vs the cloud pipeline

Where to go next