← ClaudeAtlas

triagelisted

Triage a JIRA ticket - a bug to a proven root cause (Sentry, logs, live data, code at the deployed SHA, competing causes decided by running their checks), or a question ticket to a short answer per ask. Bottom line first, load-bearing claims verified by darkmoon, facts only a person can see asked for before answering, and a ready-to-post ticket note. --fast skips the verification pass.
sgtlaugh/skills · ★ 2 · AI & Automation · score 76
Install: claude install-skill sgtlaugh/skills
# /triage - JIRA Ticket Triage Investigate a JIRA ticket end-to-end and answer what it asks: a bug gets a proven root cause, a question gets an answer per ask. Either way the reader sees the answer first, and the evidence after. ## Usage ``` /triage PROJ-1234 # triage by ticket ID /triage <jira-url> # triage by URL /triage PROJ-1234 --fast # skip the independent verification pass (Step 5) for a quick look ``` **Service catalog:** read `~/.config/claude-skills/services.md` in Step 1 - it names the log search skill, the data lookup skill, the GitHub org, and per service its repo, Sentry project, log service and notes (compiled frames, which frontend is which). Tracing without it is guessing; a value it lacks is asked for or marked inferred, never invented. ## Output contract - the triage is NOT done until it shows The order is fixed: the answer first, the evidence last ("bottom line up front"). Everything above `Details` fits on one screen: **at most 15 lines before the ticket note** - count them before showing; more is WRONG, and the excess moves under Details. A table cell holds at most 15 words; anything longer is a bullet, since a long cell wraps into an unreadable block in a terminal. **Both shapes, top to bottom:** 1. **Head** - the shape's head block (bug: TL;DR + verdict; question: the ask + the answer table), Step 6. 2. **Needs you** - facts only a person can get (Step 4's gate) and decisions that are yours (policy, owner, priority).