linear-triage

Verifies Linear backlog tickets against the codebase and posts evidence-backed triage comments.

4|Updated Oct 24, 2025
One-click install
npx skills add https://github.com/sethdavis512/iridium --skill linear-triage-sethdavis512
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: linear-triage
Source: https://github.com/sethdavis512/iridium/tree/main/.claude/skills/linear-triage
Command: npx skills add https://github.com/sethdavis512/iridium --skill linear-triage-sethdavis512

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Backlog tickets often describe work already done, reference code that never existed in this repo, or arrive imported from other projects. This Skill verifies each ticket's claims against the actual codebase before anyone spends implementation time on it. ## Core Features & Use Cases - Claim verification: Extracts checkable claims (file paths, symbols, CSS classes, env vars) from each ticket and confirms or refutes them with grep and git history. - Classification: Labels each ticket as valid-safe, valid-needs-render, valid-large, already-done, not-applicable, or unclear. - Evidence-backed comments: Posts a single triage comment per ticket with file:line evidence, without changing issue state, assignee, or labels. - Use Case: Run it on a schedule against the Iridium Linear project to comb through backlog and unstarted issues, skipping already-triaged tickets and producing a summary table with next-action recommendations. ## Quick Start Ask the assistant to triage the Linear backlog and verify each ticket against the codebase.

Frequently Asked Questions about linear-triage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I triage a Linear backlog against my codebase?

Fetch backlog and unstarted issues via the Linear MCP list_issues tool, extract each ticket's checkable claims, then grep the repository for referenced files, symbols, and classes. Classify each ticket and post one evidence-backed comment per issue.

How to verify if a ticket describes work already completed?

Check whether the described end-state already exists in the code by searching for the referenced files and symbols, and run git log on relevant files to see recent changes. Past-tense descriptions like "Added" or "Fixed" usually indicate completed work.

Does Linear triage change ticket status or assignees?

No. The triage workflow only posts a comment starting with "Triage:" containing the verdict and evidence. It never changes issue state, assignee, or labels unless the user explicitly requests state updates.

What happens to tickets that reference code the repo doesn't have?

Tickets referencing nonexistent files, classes, or features are classified as not-applicable, typically indicating they were imported from another repository. The triage comment records what was grepped and came up empty.

When should a ticket be classified as unclear instead of valid?

Classify a ticket as unclear when no checkable claim can be extracted or when verification would require more than about five tool calls, such as deep architecture reading. The comment should state what information is missing.