← ClaudeAtlas

skillsaw-issue-triagelisted

Triage a GitHub issue filed against skillsaw — classify it (bug, feature, docs, question, other), verify its claims against the codebase, enrich it with missing details, and post one structured triage comment. Use when triaging and labeling incoming issues, not to fix them.
stbenjam/skillsaw · ★ 73 · AI & Automation · score 90
Install: claude install-skill stbenjam/skillsaw
# skillsaw Issue Triage Triage a single open issue on the **skillsaw** linter. Check what kind of issue it is, check whether its claims hold up against the actual code, fill in the details it is missing, review the evidence, and leave one triage comment. This skill **triages** issues — never fix them here (that job belongs to `skillsaw-issue-solver`). Read the detailed evaluation checklist for each classification in `references/`, and read **only** the checklist for the class the issue falls into (progressive disclosure). Keep this file lean and pull the checklist in on demand. ## Step 1 — Read the Issue Run this for the issue number you were given: ```bash gh issue view <number> --json number,title,body,labels,author,comments,createdAt ``` Read the title, body, and every comment before judging anything. Note the skillsaw version the reporter names (or none), and check any config, command, or file content they pasted. ## Step 2 — Classify Set exactly one primary class. When an issue spans two, pick the one that determines the next action and note the secondary in the comment. | Class | The issue is… | Evaluation checklist | |---|---|---| | `bug` | A claim that skillsaw behaves incorrectly — wrong violation, crash, false positive/negative, bad autofix | [`references/bug-evaluation.md`](references/bug-evaluation.md) | | `feature` | A request for new behavior — a new rule, flag, config option, output format, or tool/format support | [`references/feature-evaluation.md`](