yuniorsf

Orchestrate Tickets — Git skill for Claude Code

Git community

Run multiple Jira tickets in parallel, each in its own isolated git worktree, each implemented and shipped by its own worker agent (via /ship-ticket), then rebase and merge all of them back into de.

How to install Orchestrate Tickets

Installs to ~/.claude/commands/yuniorsf-geoassets-orchestrate-tickets.md

Terminal
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/yuniorsf/GeoAssets/HEAD/.claude/commands/orchestrate-tickets.md -o ~/.claude/commands/yuniorsf-geoassets-orchestrate-tickets.md

Restart Claude Code, or start a new session, for it to be picked up.

What Orchestrate Tickets does

Run multiple Jira tickets in parallel, each in its own isolated git worktree, each implemented and shipped by its own worker agent (via `/ship-ticket`), then rebase and merge all of them back into `develop` one at a time, resolving conflicts by handing them back to the worker that wrote the conflicting change. Argument: either a space/comma-separated list of ticket keys (e.g. `XD01-180 XD01-181 XD01-182`), or `JQL: ` (e.g. `JQL: project = XD01 AND status = "To Do" AND sprint in openSprint

Alternatives in Git

  • Swarm Parent — You are the swarm coordinator for the {{tentacleName}} tentacle 1.4k ★
  • Merge Gate — Merge worker branches one-by-one with score-based accept/reject 399 ★
  • Ship Ticket — Ship an ALREADY-BUILT ticket — code review → PR → merge → learnings → install-local 85 ★

Full documentation available on GitHub

View Source Repository