Linear Bug Triage

Linear Bug Triage

Use this skill after a bug or regression candidate has measured evidence. This skill owns Linear search, deduplication, evidence comments, and filing new issues once a human says yes; the calling skill owns deciding whether the signal is issue-worthy.

What This Skill May Write

Every write carries a label and is marked as agent-written in the text, and only three write shapes are permitted at all. linear-agent-writes is the authority for that policy; read it before your first write and prefer it over this summary wherever they differ.

For this skill it resolves to:

• An evidence comment on an issue that already exists: propose, then post. Show the comment body in the findings table, get a yes (one go-ahead can cover the whole set), then post it and label that issue AI commented. Mark the comment body as agent-written.
• A new top-level issue: ask once, then file it. A bug cluster surfaced by a review has no parent, and a parentless ticket needs a go-ahead. Take one go-ahead for the whole set, or for named rows — never one question per candidate.

So present the findings table either way: it is what the go-ahead is given against, and it is the report afterwards. One row per candidate:

• Candidate / cluster name.
• Environments.
• Service and route/resource.
• Recent window measurement.
• Baseline measurement.
• Delta / regression summary.
• Key evidence links — the ones Required Evidence below asks for.
• Action: awaiting your go-ahead with the exact comment or ticket body, commented <issue key> once approved and posted, or filed <issue key> once a row is approved and created.