ticket-ship

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

Skill by OutThisLife

IndexedMIT★ 206

Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/outthislife-ticket-ship

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

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.

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools: No tools found
Secrets: None asked for
Install scripts: None found

Network hosts it talks to 1

codeload.github.com · found in install command

Files it touches

~/.claude/skills/ticket-ship

What's inside

Skill 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.
License: MIT
Instructions: 24 lines in SKILL.md · view on GitHub

Files (1)

SKILL.md

SKILL.md (first lines)

# 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.

From OutThisLife/brooklyn-skills, MIT.

Signals

Stars: 206
Forks: 6
Open issues: 0
Last commit (this folder): Sep 25, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

License: MIT
Repository: github.com/OutThisLife/brooklyn-skills
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: GitHub github-graphql

More from OutThisLife

Cite this page

ticket-ship skill. Agent Mart. https://agentmart.dev/skills/outthislife-ticket-ship (last updated 2026-10-24)