Ticket → Ship
SkillCommunicationTake 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.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Ticket → Ship skill
What this skill tells your AI
The instructions your AI receives, as published by outthislife/brooklyn-skills in skills/ticket-ship/SKILL.md and read by ahel’s review.
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 list the assigned work (
acli, Jira, Linear, etc.). - 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). - Move the ticket to the right state (In Review / Test / whatever this tracker uses). Link the PR on the ticket.
- 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.
Signals
- GitHub stars
- 192
- Forks
- 6
- Last commit
- Aug 2026
Advanced
- Catalog kind
- skill
- Gateway key
ticket-ship- Source
- github.com/outthislife/brooklyn-skills