Burn Jira — Development skill for Claude Code
Run one unattended pass of burn process jira over labelled Jira tickets — one session per ticket, stopping at a quota threshold.
How to install Burn Jira
Installs to ~/.claude/skills/tbobm-dont-burn-it-all-burn-jira/SKILL.md
mkdir -p ~/.claude/skills/tbobm-dont-burn-it-all-burn-jira && curl -fsSL https://raw.githubusercontent.com/tbobm/dont-burn-it-all/HEAD/commands/burn-jira.md -o ~/.claude/skills/tbobm-dont-burn-it-all-burn-jira/SKILL.md Restart Claude Code, or start a new session, for it to be picked up.
What Burn Jira does
name: burn-jira description: Run one unattended pass of `burn process jira` over labelled Jira tickets — one session per ticket, stopping at a quota threshold. Previews first; does not babysit.
Run `burn process jira` **once** for the user and report its digest. Do NOT loop or re-invoke it — each `/burn-jira` is a single bounded pass. A schedule (cron, launchd, a systemd timer, a Routine) decides when it runs again.
Steps:
- Build the binary if it is missing: `test -x "${CLAUDE_PLU
Alternatives in Development
- Release & Shipping Burn Patterns — Research Summary — Research completed: 2026-02-10 Sources: ~/.claude/CLAUDE.md (This Has Burned You Before table), SESSION_HANDOF 216 ★
- Atlassian Integration — Integrate with Jira, Confluence, and Bitbucket 159 ★
- Jira.Log — Log a new Jira issue to RHOAIENG with Team (Ambient team) and Component (Agentic) pre-filled 129 ★
Full documentation available on GitHub
View Source RepositoryRelated Skills
Ticket Triage
Pull all assigned Jira tickets, categorize by priority and status, detect stuck work, and recommend what to wo
Writing Hooks
Claude Code / Cowork skill that generates scroll-stopping opening lines for any content. 5 hooks per run acros
Claude Code Intelligence
Local-first usage intelligence for Claude Code: an OTLP receiver, transcript parsing and quota tracking that a
Cctally
Claude Code usage tracker and local dashboard for Pro/Max subscription limits - weekly cost-per-percent trend,
Istari Plan
Intelligent planning command that decomposes Jira tickets into actionable beads with dependencies
Get Jira Diff
Utility: Fetch Jira tickets and diff each against the current codebase — surface what is implemented, partial,
Related Agents
Executor Opus High
Ticket executor for tickets where the executor decides things a later ticket builds on — Opus at high reasonin
Jira Ticket Transitioner
Transitions Jira tickets between workflow states using ACLI (Atlassian CLI)
Jira Ticket
Create or update Jira tickets using the Atlassian CLI