Menu
One-time setup for the Linear triage automation workflow. Verifies prerequisites, creates the "Claude Code" label in Linear, and registers the RemoteTrigger that polls every 15 minutes. Run this once before using /linear-triage-poller.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
End-to-end worker for a single Linear issue. Reads the issue, plans an implementation, creates an isolated git worktree, implements the solution, opens a draft PR linked to the Linear issue, runs tests, marks the PR ready for review, and notifies the assignee. Invoked by /linear-triage-poller with an issue ID argument.
Poll the Linear triage queue every 15 minutes for issues labeled "Claude Code" and delegate each one to /linear-issue-worker. Intended to be triggered by the RemoteTrigger registered via /linear-triage-setup. Can also be run manually to trigger immediately.
Audit a Linear team's labels and report stale ones. Generates a tiered cleanup report (unused / low-use & stale / legacy) based on issue count and most-recent application date. Use when a team lead asks to "find stale labels", "clean up labels", "audit labels", or "which labels are unused" for a specific team.
Baseado na classificação ocupacional SOC
| name | linear-triage-setup |
| description | One-time setup for the Linear triage automation workflow. Verifies prerequisites, creates the "Claude Code" label in Linear, and registers the RemoteTrigger that polls every 15 minutes. Run this once before using /linear-triage-poller. |
You are setting up the Linear Triage Automation system. Execute each step in order and report the result of each.
Run these checks in parallel:
# 1a. gh CLI authenticated?
gh auth status
# 1b. Config file exists?
cat ~/.claude/linear-triage-config.json 2>/dev/null || echo "CONFIG_MISSING"
If gh auth status fails: stop and tell the user to run gh auth login first.
If CONFIG_MISSING: stop and tell the user to copy the example config:
cp <plugin-dir>/config.example.json ~/.claude/linear-triage-config.json
$EDITOR ~/.claude/linear-triage-config.json
They must set repo, repoUrl, and team before continuing. Re-run /linear-triage-setup once the config is in place.
Read ~/.claude/linear-triage-config.json and confirm these fields are set (not the placeholder values from the example):
repo — exists OR repoUrl is set so it can be clonedteam — set to a real Linear team key (not "YOUR_TEAM_KEY")label — defaults to "Claude Code" if absentIf repo does not exist locally and repoUrl is unset, stop and ask the user to set repoUrl.
If repo exists locally, verify it has a git remote:
cd <repo from config> && git remote -v
If no remote: stop and tell the user to configure one.
Use mcp__claude_ai_Linear__create_issue_label to create a label named the value of label (default "Claude Code") with color #7C3AED (purple). If the tool errors with "already exists", that's fine — skip and continue.
Use the schedule skill or RemoteTrigger tool to create a scheduled remote agent with:
*/15 * * * */linear-triage-pollerPrint a summary:
✅ Linear Triage Automation — Setup Complete
Prerequisites: ✅ gh CLI authenticated / ✅ git remote configured
Config: ~/.claude/linear-triage-config.json
Label created: "<label>" (apply this label to any triage issue you want Claude Code to handle)
RemoteTrigger: */15 * * * * → /linear-triage-poller
Next steps:
1. Tag a triage issue with "<label>" in Linear
2. The poller will pick it up within 15 minutes
3. Or run /linear-triage-poller manually to trigger immediately