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