← ClaudeAtlas

rig-issuelisted

Create, view, move, or manage tickets in the project's issue tracker (Linear, GitHub Issues, or none). Triggers on: 'ticket', 'create ticket', 'move ticket', 'ticket board', 'show tickets', 'list tickets'.
agent-rig/rig · ★ 3 · AI & Automation · score 70
Install: claude install-skill agent-rig/rig
# Ticket Manager Manage tickets in whatever issue tracker the project is bound to. The tracker is **config-driven** — read `.rig/config.json` first and dispatch on `tracker.provider`. Never hardcode a team or project name. ## Configuration Reads `.rig/config.json` (missing keys → defaults): | Key | Default | Used for | |---|---|---| | `tracker.provider` | `none` | `linear` \| `github` \| `none`. Selects the backend. | | `tracker.team` | — | Linear team name/key, or GitHub org, scoping list/create. | | `tracker.project` | — | Linear project name for list/create. | | `tracker.ticketPrefix` | — | Identifier prefix (e.g. `ABC-`) to recognize IDs. | | `tracker.labelMapFile` | `.claude/label-mapping.md` | Label source-of-truth for create. | | `tracker.githubIntegration` | `false` | If true, do NOT manually move states (see below). | **If `tracker.provider` is `none`:** this skill can't run. Explain that ticket management needs a tracker, and point the user at `.rig/config.json` → set `tracker.provider` to `linear` or `github` (with `team`/`project`). Stop there. ## Arguments The user invoked this with: $ARGUMENTS ## Actions Parse the user's request as one of the actions below. Each action lists the Linear and GitHub form — use the one matching `tracker.provider`. ### `board` or `list` (default if no args) - **Linear:** `mcp__claude_ai_Linear__list_issues` with `project` = `tracker.project`, `team` = `tracker.team`, `limit: 100`. - **GitHub:** `gh issue list --limit 100