
Ticket Lifecycle (Deckhand)
- 6 repo stars
- Updated July 3, 2026
- jonthebeef/deckhand
Ticket Lifecycle (part of deckhand) is a Claude Code skill that automates batch ticket processing on a GitHub Projects v2 board - implementing issues in parallel git-worktree subagents, running an isolated PR review loop
About
Ticket Lifecycle is one half of deckhand, a pair of Claude Code skills for running AI-assisted delivery on a GitHub Projects v2 board. It takes a set of issues and processes them end-to-end - implementing each ticket (optionally in parallel subagents, each in its own git worktree), running an isolated fresh-context code-review agent, looping on review feedback up to five rounds, waiting for CI to pass, merging, and moving the card to Done. It is modular: a solo, single-ticket, sequential run uses the same phase discipline without the parallelism. Everything runs through the gh CLI, so no extra SaaS, API, or glue code is needed, and it works in Codex as well as Claude Code.
- Parallel ticket delivery in isolated git worktrees
- Fresh-context isolated PR review agent per change
- Review-fix loop up to 5 rounds, waits for CI green
- Auto-moves kanban cards Doing -> Review -> Done
- Works in both Claude Code and Codex via gh CLI
Ticket Lifecycle (Deckhand) by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
npx skills add https://github.com/jonthebeef/deckhand --skill ticket-lifecycleAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| repo stars | ★ 6 |
|---|---|
| Last updated | July 3, 2026 |
| Repository | jonthebeef/deckhand ↗ |
What it does
Hand a batch of GitHub issues to Claude Code and have it implement, review, CI-gate, and merge each one in parallel worktrees, moving cards across the kanban automatically.
Who is it for?
Best when you run a GitHub Projects v2 board and want your coding agent to take a batch of tickets from implementation through isolated review, CI, and merge without manual hand-holding.
Skip if: Not for teams that track work outside GitHub Projects, or who want a hosted SaaS tracker - it is driven entirely through the gh CLI and a Projects v2 board.
What you get
Point the skill at an epic or a set of issue numbers and it delivers them in parallel, each PR reviewed by a fresh isolated agent and merged only once CI is green, with the kanban kept in sync automatically.
By the numbers
- Review-fix loop runs up to 5 rounds per PR
- Two paired skills: ticket-lifecycle + managing-project-backlog
- Maps to six workflow states (Epics/Backlog/Prioritized/Doing/Review/Done)
Files
Ticket Lifecycle
Automated batch ticket processing for any GitHub-Projects-driven repo. Take a set of GitHub issues, implement fixes, run code review, address feedback, watch CI, merge when green, and move tickets across the Kanban board.
The full Phase 0->7 sequence is the ideal run: many tickets in parallel worktrees, fresh-context reviewers. But the value is the discipline of the phases, not the parallelism - the skill is modular, so a solo/single-ticket sequential run still uses Phase 0 (load learnings), Phase 3 (isolated review), Phase 3.5 (capture learnings), Phase 4 (review loop), Phase 6 (merge), Phase 7 (cleanup). Each PR gets a fresh, isolated review agent; the skill actions the feedback in a loop (up to 5 rounds) and waits for CI green at each step.