A release workflow for code that is already built on the current feature branch. It reviews the changes, opens and merges a pull request, records learnings, and reinstalls the local result.

Use it to ship a finished ticket, with checks for review results, pull-request status, merge readiness, and local installation.

It provides the review and delivery steps without rebuilding work that is already complete.

How alfredoperez/speckit-companion configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to alfredoperez/speckit-companion. 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/alfredoperez/speckit-companion/main/.claude/commands/ship-ticket.md

Clone the repo

git clone --depth 1 https://github.com/alfredoperez/speckit-companion

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/alfredoperez/speckit-companion/ship-ticket/github.svg)](https://agentmods.dev/commands/alfredoperez/speckit-companion/ship-ticket)

Your own site

<a href="https://agentmods.dev/commands/alfredoperez/speckit-companion/ship-ticket"><img src="https://agentmods.dev/badge/commands/alfredoperez/speckit-companion/ship-ticket/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/alfredoperez/speckit-companion/ship-ticket"><img src="https://agentmods.dev/badge/commands/alfredoperez/speckit-companion/ship-ticket.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 2,512 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.00046	$0.02512
Opus 5	$0.00023	$0.01256
Sonnet 5	$0.00009	$0.00502
Haiku 4.5	$0.00005	$0.00251

Measured today against content hash c7783ec261e5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

ship-ticket 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 today.

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-ticket.md · 114 lines

How it starts

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

What this does

The post-build tail for a ticket you built yourself in SpecKit Companion (GUI / /speckit.companion.*). It does not rebuild — it takes the committed work on the current feature branch and ships it: review, PR, merge, learnings, reinstall. It is /fix-tickets steps 3–8 with the build skipped.

Use /fix-tickets when you want the loop to build the fix too. Use /ship-ticket when the code already exists on a branch and you just want the review→merge tail.

Locked defaults

Never rebuild. The branch already has the work; this command only reviews/ships it.
Never merge red checks. Leave the PR open and report.
Auto-merge on unless --review-merge is passed (then pause for a thumbs-up before gh pr merge).
/code-review is the review gate — high effort, findings applied; re-run it on any fix that itself changes real logic (the fix commit is the least-reviewed code).
Heavy steps run in subagents (review, distilling learnings); the main loop only does git/gh/decisions.

Inputs

$ARGUMENTS:

An issue number (292) — preferred.
Empty → derive from the current branch name (NNN-slug → look up the issue), confirm before proceeding.
--review-merge anywhere → pause before merge.

Procedure

Run from the repo root (~/dev/GitHub/speckit-companion). Confirm with git rev-parse --show-toplevel.

0. Preconditions — main loop

git rev-parse --show-toplevel                 # must be speckit-companion
git branch --show-current                     # must NOT be main; expect NNN-slug
git status --porcelain                        # work should be committed; a clean tree is ideal

Refuse if on main — there's nothing to ship. Stop and report.
Resolve the issue number from $ARGUMENTS or the branch's NNN. gh issue view <N> to capture title/body for the PR + verify it's still open. If you can't resolve an issue, ask (AskUserQuestion) — a PR still wants a Closes #N.
If there are uncommitted changes that are the real work, commit them first (real change + specs/<NNN>/ spec folder); do not commit .specify/ regenerated artifacts (git checkout origin/main -- .specify/<file> for any swept in).

Read the full file on GitHub · 114 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.

today Changed · +3 lines c7783ec261e5
yesterday Changed · +6 lines b296f092b8ab
11d ago First seen · 105 lines · 46 tokens per session scan A c4a51b411585

Subscribe to this mod's changes

ship-ticket is a command published in the GitHub repository alfredoperez/speckit-companion (90 stars, last pushed today), licensed MIT. It adds 46 tokens to every session and 2,512 once invoked, about $0.0002 per session on Opus 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-30.

Claude Code Code review Git and workflow TypeScript ai-tools developer-tools spec-driven-development vscode-extension

pr-ready

Run the project's pre-commit review loop to determine whether the current branch is ready to push — lint, tests, parallel pr-review-toolkit agents plus an over-engineering audit, fix-and-re-run until convergence.

costajohnt/oss-autopilot · 45 tokens

pr-package

Prepare a clean delivery package for GitHub from the real git diff vs an explicit base branch, persisted as PRPACKAGE.md (or PRPACKAGE. .md for multi-repo tasks). Produces branch name, commit messages, fetch, checkout, add, commit, and push commands, PR title and body, and reviewer attention points; never invents work…

Mozurok/fhorja.dev · 216 tokens

speckit-companion: Command for Claude Code