A workflow for taking a Jira or Linear tracker ticket through development to a shippable change. It connects the ticket with its pull request, review status, merge state, and stakeholder update.

Use it to read assigned work, verify the correct base branch, find or start a pull request, resolve its readiness issues, update the ticket state, link the pull request, and draft a short status message.

It reduces gaps between the work described in a ticket and the actual code-review process. It also prevents tickets being marked complete while checks or review work remain open.

ticket-ship — Skill for Claude Code and Codex by OutThisLife

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add OutThisLife/brooklyn-skills --skill ticket-ship

Clone the repo

git clone --depth 1 https://github.com/OutThisLife/brooklyn-skills

Made for: Claude Code, Codex.

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/skills/outthislife/brooklyn-skills/ticket-ship/github.svg)](https://agentmods.dev/skills/outthislife/brooklyn-skills/ticket-ship)

Your own site

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

Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 456 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. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.00049	$0.00456
Opus 5.5	$0.00020	$0.00182
Sonnet 5.5	$0.00010	$0.00091
Haiku 4.5	$0.00005	$0.00046

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

Security

Grade A, and why

ticket-ship 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 1mo 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.

skills/ticket-ship/SKILL.md · 31 lines

What it actually says

Ticket → Ship

The ticket-shaped parts of shipping. The PR mechanics live in their own skills — this is what a tracker adds on top.

Steps

Read the ticket and its latest comments, then list existing PRs before starting (acli, Jira, Linear, gh). With acli, request --fields summary,description,status,comment,issuelinks --json: the default view omits comments, which can contain reopened QA scope. Read the existing PR diff as well as its body; follow-up commits can invalidate the body's implementation claims.
Confirm the correct base branch(es) before starting — some orgs need a release branch plus the default (stacked-pr). Never assume; verify the org's rule.
Find the existing PR or start one (work → pr-update), then drive it mergeable (pr-ready) and polish before handoff (clean).
Read the repository's ticket/label guidance before selecting a handoff state; don't substitute generic workflow names. In MR, use .claude/skills/create-pr/SKILL.md and teams.md for label rules. For an existing DOTCOMPB PR returned by QA and then fixed, the user's retest handoff is In Test with Pending QA Review, not a reset to In Code Review. Preserve the ticket-driven Needs UI Review label. Report CI/deployment blockers separately; In Test does not mean merge-ready. Link the PR and add a factual retest update when the user requests the handoff.
Draft the stakeholder update — Slack or a ticket comment, short, no-tropes. Don't send it unless asked.

Don't

Assume the base branch.
Mark the ticket done while CI is red or review threads are open.
Let the ticket and the PR tell different stories about the state of the work.

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.

1mo ago Changed · -1 lines 62f32b906da5
2mo ago First seen · 32 lines · 49 tokens per session scan A 5f45a2c343db

Subscribe to this mod's changes

ticket-ship is a skill published in the GitHub repository OutThisLife/brooklyn-skills (209 stars, last pushed 7d ago), licensed MIT. It adds 49 tokens to every session and 456 once invoked, about $0.0002 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-30.

Git and workflow Project management

antfu-issue-triage

Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate, and spam items, suggest labels, gauge demand from reactions and comments, then present a table of proposed actions and comments for confirmation before touching anything. Use when asked to triage, organize, clean up, or groom issues…

antfu/skills · 76 tokens

mcore-split-pr

Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.

NVIDIA/skills · 25 tokens

engineer-bot-ops

A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.

makecindy/cindy · 57 tokens

shiplog

Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.

aeonfun/aeon · 46 tokens

connect

Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…

nimbalyst/nimbalyst · 101 tokens

llxprt-issue-workflow

Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the zai-glm-flash smoke test), open code review (ocr)…

vybestack/llxprt-code · 88 tokens