A command that takes one or more GitHub issues through planning, implementation, code review, pull-request creation, and status watching. A pull request is a proposed code change submitted for review before merging.

Use it to coordinate several GitHub issue fixes, including separate worktrees, parallel implementation, review fixes, branch verification, and pull requests.

It organizes the full issue-to-pull-request process and pauses for approval at defined points. It also checks that implementation agents changed only the files allowed by the plan.

How richardthe3rd/cambridge-beer-festival-app configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to richardthe3rd/cambridge-beer-festival-app. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/richardthe3rd/cambridge-beer-festival-app/main/.claude/commands/ship-issues.md

Clone the repo

git clone --depth 1 https://github.com/richardthe3rd/cambridge-beer-festival-app

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/richardthe3rd/cambridge-beer-festival-app/ship-issues/github.svg)](https://agentmods.dev/commands/richardthe3rd/cambridge-beer-festival-app/ship-issues)

Your own site

<a href="https://agentmods.dev/commands/richardthe3rd/cambridge-beer-festival-app/ship-issues"><img src="https://agentmods.dev/badge/commands/richardthe3rd/cambridge-beer-festival-app/ship-issues/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/richardthe3rd/cambridge-beer-festival-app/ship-issues"><img src="https://agentmods.dev/badge/commands/richardthe3rd/cambridge-beer-festival-app/ship-issues.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 605 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00015	$0.00605
Opus 5.5	$0.00006	$0.00242
Sonnet 5.5	$0.00003	$0.00121
Haiku 4.5	$0.00002	$0.00060

Measured 2mo ago against content hash 21ba1ae5e8af, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ship-issues scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/commands/ship-issues.md · 58 lines

How it starts

The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Ship Issues

Full plan → implement → review → fix → PR → watch cycle for one or more GitHub issues.

Usage: /ship-issues #270 #324 #355

Workflow

Work through these stages in order. Pause for user approval at each ✋ gate.

Stage 1 — Plan

Invoke /plan-issues for all issue numbers. Present plans. ✋ Wait for approval.

Stage 2 — Implement

For each approved plan, spawn an implementation agent with isolation: "worktree":

Branch name: fix/<issue-number>-<short-slug> (created inside the worktree)
Pass: phase steps, allowed-file manifest as a hard constraint, explicit "do not modify files outside this list"
The agent must run ./bin/mise run check before committing and push to its branch

Run all implementation agents in parallel.

After all agents complete, verify each branch:

git diff $(git merge-base main fix/<issue-number>-<short-slug>)..fix/<issue-number>-<short-slug> --stat

Confirm only planned files changed. ✋ Flag any drift before continuing.

Stage 3 — Review

Run /address-review across all fix branches. Apply fixup commits for clear findings. ✋ Ask about ambiguous ones.

Stage 4 — Push PRs

Create one PR per fix branch targeting main. PR body must include Fixes #<issue-number> to auto-close the issue on merge, plus a brief summary of changes. Subscribe to all PRs with mcp__github__subscribe_pr_activity.

Stage 5 — Watch

Monitor CI and review activity. For each event:

Green CI on all checks → nothing to do
Test/analyze failure → diagnose and push a fix commit
Copilot/automated review comment → invoke /address-review on that PR
Human review comment → surface to user if ambiguous, otherwise fix and push

The session ends when all PRs are green and have no unresolved review threads.

Notes

Implementation agents use isolation: "worktree" — this creates worktrees inside the repo at .claude/worktrees/, which is required for commit signing in the managed environment.
Fix branches target main directly. The session branch (claude/session-*) is for session-level changes (AGENTS.md updates, etc.).
Always run ./bin/mise run commands, never raw flutter — see AGENTS.md for the full command reference.
MCP tool parameters take plain strings — no $(cat <<'EOF'...) heredoc syntax in body fields (see AGENTS.md → "GitHub MCP Notes").

Read the full file on GitHub · 58 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 58 lines · 15 tokens per session scan A 21ba1ae5e8af

Subscribe to this mod's changes

ship-issues is a command published in the GitHub repository richardthe3rd/cambridge-beer-festival-app (3 stars, last pushed today), licensed MIT. It adds 15 tokens to every session and 605 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Git and workflow Planning

ship-issues next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
ship-issuesrichardthe3rd/cambridge-beer-festival-app	Command	3	today	MIT	A	15	Claude Code
merge-conflict-analysisrjmurillo/ai-agents	Command	49	yesterday	MIT	A	0	GitHub Copilot
release-notesOpenHands/extensions	Command	176	yesterday	MIT	A	44	Claude Code
commitechoVic/blade-code	Command	181	24d ago	MIT	A	8	Claude Code
repo-audittractorjuice/arc-kit	Command	2.3k	3d ago	none	A	29	Claude Code
propsmill/infrahub-mcp	Command	10	yesterday	Apache-2.0	A	18	Claude Code
codex-reviewoalders/kitchen-sink	Command	5	4d ago	MIT	A	41	Claude Code

cambridge-beer-festival-app: Command for Claude Code