merge-ticket
Installation
SKILL.md
merge-ticket
Essential Principles
- Both modes run this same skill. Local mode executes the workflow in this session; remote mode hands the ticket's agent a prompt naming this skill, and that session recognises itself as the ticket's agent and self-selects local mode - so the guardrails reach whichever session executes.
- The executing session needs context this skill doesn't carry: which MR(s), which worktree, which ticket. A ticket's implement-ticket agent has all three, which is why remote mode targets it by name and never spawns a replacement. In local mode, discover them from the current branch and conversation, and ask rather than guess when ambiguous.
- Merging is irreversible and the workflow ends by closing the ticket, so "all issues fixed or answered" is a hard gate. Never merge past an unaddressed review comment. Every push (fixes or a rebase) stales all earlier reads of CI and comments - "return to step 1" means re-reading both, not resuming from memory.
Parameters
| Param | Required | Notes |
|---|---|---|
ticket_id |
no | Ticket ID; presence selects remote mode, subject to the agent's state. A bare issue number (42, #42) names its agent only with the repo, so run from the ticket's repo |
Process
Step 1: Dispatch
Run by its absolute path under this skill's directory: