Agent skill

Ticket Ship

by OutThisLife in OutThisLife/brooklyn-skills

Take a tracker ticket through to shipped: find or start the PR, drive it to mergeable, update the ticket state, draft the stakeholder message.

MITAuto-check passed

Install Ticket Ship

skills CLI
$ npx skills add OutThisLife/brooklyn-skills --skill ticket-ship -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install OutThisLife/brooklyn-skills ticket-ship --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/OutThisLife/brooklyn-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/ticket-ship .claude/skills/ticket-ship && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
ticket-ship
GitHub stars
199
Token cost
~486 tokens
SKILL.md length
257 words
Files
1
Skills in repo
22
Repo updated
First seen
Licence
MIT

At a glance

Take a tracker ticket through to shipped: find or start the PR, drive it to mergeable, update the ticket state, draft the stakeholder message.

  • Works in 5 steps: Read the ticket and its latest comments,… → Confirm the correct base branch(es)… → Find the existing PR or start one (work… → …
  • Jira/Linear (or acli) tickets assigned to you
  • SKILL.md covers Steps and Don't
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Ticket Ship is an agent skill from OutThisLife/brooklyn-skills. Take a tracker ticket through to shipped: find or start the PR, drive it to mergeable, update the ticket state, draft the stakeholder message. Use for Jira/Linear (or acli) tickets assigned to you.

Its SKILL.md is about 490 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It works with Jira. The repository describes itself as: Skills that drive best-in-class engineering. The licence is MIT.

When your agent uses it

  • Jira/Linear (or acli) tickets assigned to you

Example prompts

  • “/ticket-ship”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Read the ticket and its latest comments, then list existing PRs before starting (acli, Jira, Linear, gh). With acli, request --fields…
  2. Confirm the correct base branch(es) before starting — some orgs need a
  3. Find the existing PR or start one (work → pr-update), then drive it
  4. Read the repository's ticket/label guidance before selecting a handoff state; don't substitute generic workflow names. In MR, use…
  5. Draft the stakeholder update — Slack or a ticket comment, short, no-tropes.

What it can do on your machine

Read from SKILL.md and the folder at commit 8a97904. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Ticket Ship loads about 486 tokens when it runs. Until then it costs about 52 tokens; SKILL.md has 257 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~52
When it runs · the whole SKILL.md, loaded when a task matches
~486

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from OutThisLife/brooklyn-skills at commit 8a97904, republished under its MIT licence (© OutThisLife). 257 words, ~486 tokens.

Download SKILL.mdSave it as .claude/skills/ticket-ship/SKILL.md (or your agent's skills folder).
name
ticket-ship
description
Take a tracker ticket through to shipped: find or start the PR, drive it to mergeable, update the ticket state, draft the stakeholder message. Use for Jira/Linear (or acli) tickets assigned to you.

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

  1. 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.
  2. 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.
  3. Find the existing PR or start one (work → pr-update), then drive it mergeable (pr-ready) and polish before handoff (clean).
  4. 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.
  5. 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.

© OutThisLife, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/ticket-ship of OutThisLife/brooklyn-skills.

Open the folder on GitHubat commit 8a97904

Compare with similar skills

Ticket Ship next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Ticket Ship compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Ticket Ship this skillOutThisLife/brooklyn-skills199—~486Automated safety check: PassMIT
Management Talkthananon/9arm-skills3.2k—~3.2kAutomated safety check: PassNone
YugabyteDB Issue Creatoryugabyte/yugabyte-db11k—~2kAutomated safety check: PassCustom licence
Dynamo Jira TicketDynamoDS/Dynamo2k—~1.1kAutomated safety check: PassApache-2.0
Code Reviewcroffasia/itsaplan913—~2kAutomated safety check: PassAGPL-3.0
Connect Apps with ComposioComposioHQ/awesome-claude-skills77k3 repos~557Automated safety check: PassNone

Similar skills

  • Management Talk

    thananon/9arm-skills

    Rewrite engineer-to-engineer content for engineering-org leadership (VPs, directors, PMs, release managers, execs in an engineering-savvy company) and shape it for the channel it is going to — JIRA…

    3.2k GitHub stars~3.2k tokensUpdated 3 mo ago
    Productivity & AutomationAuto-check passed
  • YugabyteDB Issue Creator

    yugabyte/yugabyte-db

    Creates a GitHub issue or JIRA ticket for a YugabyteDB change or bug, after scrubbing customer data, secrets and unreleased details from anything public.

    11k GitHub stars~2k tokensUpdated today
    DevelopmentAuto-check passed
  • Dynamo Jira Ticket

    DynamoDS/Dynamo

    Create structured Jira tickets for Dynamo from bug reports, failing tests, or feature requests.

    2k GitHub stars~1.1k tokensUpdated today
    Testing & QAAuto-check passed
  • Code Review

    croffasia/itsaplan

    A skill your agent uses when reviewing code — a diff, a merge request, a file, a directory, or a feature.

    913 GitHub stars~2k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Connect Apps with Composio

    ComposioHQ/awesome-claude-skills

    Connects an agent to 1000+ external apps through the Composio Tool Router plugin, so it can actually send emails, create issues and post messages instead of only drafting them.

    77k GitHub starsUsed in 3 repos~557 tokens
    Productivity & AutomationAuto-check passed
  • PR Body

    SAP/spartacus

    Official

    A skill your agent uses when the user asks to generate, write, or draft a pull request (PR) body or description for the current branch.

    784 GitHub stars~499 tokensUpdated today
    DevelopmentAuto-check passed

More from OutThisLife/brooklyn-skills

All 22 skills in this repo
  • Draft Tweet

    OutThisLife/brooklyn-skills

    Draft X/Twitter posts about shipped work. An agent skill from OutThisLife/brooklyn-skills.

    199 GitHub stars~456 tokensUpdated 4 days ago
    Auto-check passed
  • Free Disk Space

    OutThisLife/brooklyn-skills

    Safely reclaim disk space on macOS without touching personal or agent data.

    199 GitHub stars~433 tokensUpdated 4 days ago
    Auto-check passed
  • List Open Work

    OutThisLife/brooklyn-skills

    List my open MRs/PRs in the current repo/worktree, each with its tracker ticket.

    199 GitHub stars~1.5k tokensUpdated 4 days ago
    Auto-check passed
  • PR Ready

    OutThisLife/brooklyn-skills

    Clear everything blocking an existing PR/MR from merging — rebase onto the default branch, get CI green, and resolve review threads (Copilot and human).

    199 GitHub stars~2.5k tokensUpdated 4 days ago
    Auto-check passed
  • PR Triage

    OutThisLife/brooklyn-skills

    Maintainer triage on OTHER people's PRs/MRs — verdict of approve, supersede, or close, salvage with credit, close the cluster.

    199 GitHub stars~4.7k tokensUpdated 4 days ago
    Auto-check passed
  • PR Update

    OutThisLife/brooklyn-skills

    Open a PR/MR if missing, or refresh an existing one's title and description so they match the current diff.

    199 GitHub stars~1.3k tokensUpdated 4 days ago
    Auto-check: notes

Works with

Questions about Ticket Ship

What does Ticket Ship do?

Take a tracker ticket through to shipped: find or start the PR, drive it to mergeable, update the ticket state, draft the stakeholder message. Ticket Ship is an agent skill from OutThisLife/brooklyn-skills. Take a tracker ticket through to shipped: find or start the PR, drive it to mergeable, update the ticket state, draft the stakeholder message.

When should I use Ticket Ship?

Ticket Ship fits situations like: jira/Linear (or acli) tickets assigned to you.

How do I install Ticket Ship in Claude Code?

Run `npx skills add OutThisLife/brooklyn-skills --skill ticket-ship -a claude-code`. Or copy the skill folder (skills/ticket-ship in OutThisLife/brooklyn-skills) into .claude/skills/ticket-ship in your project. Claude Code loads it when a task matches its description.

How do I install Ticket Ship in Codex?

Run `npx skills add OutThisLife/brooklyn-skills --skill ticket-ship -a codex`. Or copy the skill folder (skills/ticket-ship in OutThisLife/brooklyn-skills) into .agents/skills/ticket-ship in your project. Codex loads it when a task matches its description.

Can I use Ticket Ship in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add OutThisLife/brooklyn-skills --skill ticket-ship -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ticket-ship, .gemini/skills/ticket-ship, .github/skills/ticket-ship and .opencode/skills/ticket-ship in your project.

What does Ticket Ship need to run?

SKILL.md names no scripts, command-line tools or credentials: Ticket Ship is instructions for the agent only.

Does Ticket Ship access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Ticket Ship safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Ticket Ship use?

Ticket Ship is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Ticket Ship use?

About 486 tokens (SKILL.md is roughly 1.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Ticket Ship?

Skills that share tags, products or a category with Ticket Ship: Management Talk (thananon/9arm-skills, 3.2k stars), YugabyteDB Issue Creator (yugabyte/yugabyte-db, 11k stars), Dynamo Jira Ticket (DynamoDS/Dynamo, 2k stars) and Code Review (croffasia/itsaplan, 913 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Ticket Ship?

OutThisLife (a GitHub user) maintains it in OutThisLife/brooklyn-skills, which has 199 GitHub stars. The repository holds 22 skills in this directory. The repository was last updated on October 5, 2026.

Source: OutThisLife/brooklyn-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.