triage-bug
starsforks
How to install triage-bug?
spencerpauly/skills-repo/triage-bug
$npx -y skills add spencerpauly/skills-repo --skill triage-bugTake a raw bug report and turn it into a clean, prioritized ticket with a title, repro steps, and severity. Use when the user says "triage this", pastes a support escalation, or asks "what's this bug".
SKILL.md
| 1 | # Triage Bug |
| 2 | |
| 3 | Convert a noisy bug report into a ticket someone can act on: one-line title, repro steps, severity, area. |
| 4 | |
| 5 | ## When to use |
| 6 | |
| 7 | - Support escalates a bug. |
| 8 | - A teammate dumps a Slack thread or screenshot. |
| 9 | - The user says "triage this" or "what's this bug". |
| 10 | |
| 11 | ## Steps |
| 12 | |
| 13 | 1. **Re-read the report once, in full.** Don't start writing yet. |
| 14 | 2. **Restate the symptom** in one sentence as a user would say it. No internal jargon. |
| 15 | 3. **Pull out repro steps** even if the original report doesn't separate them. Number them 1, 2, 3. |
| 16 | 4. **Note the gap** between expected and actual. |
| 17 | 5. **Decide severity** with this rubric: |
| 18 | - **S1** — production down, data loss, or security issue. |
| 19 | - **S2** — common path broken, no workaround. |
| 20 | - **S3** — broken with workaround. |
| 21 | - **S4** — cosmetic / rare path. |
| 22 | 6. **Identify the area** (one of: editor, billing, auth, api, infra, marketing). |
| 23 | |
| 24 | ## Output format |
| 25 | |
| 26 | ```markdown |
| 27 | ## Title |
| 28 | <one line, present tense, no "bug:" prefix> |
| 29 | |
| 30 | ## Severity |
| 31 | S2 |
| 32 | |
| 33 | ## Area |
| 34 | billing |
| 35 | |
| 36 | ## Repro |
| 37 | 1. ... |
| 38 | 2. ... |
| 39 | 3. ... |
| 40 | |
| 41 | ## Expected vs actual |
| 42 | - Expected: ... |
| 43 | - Actual: ... |
| 44 | |
| 45 | ## Notes |
| 46 | - URLs, screenshots, affected user IDs. |
| 47 | ``` |
| 48 | |
| 49 | ## Don't |
| 50 | |
| 51 | - Don't open with "I think the issue is..." — the title goes first. |
| 52 | - Don't skip severity. Every ticket gets one, even if it's a guess. |
| 53 | - Don't paste raw stack traces into the title. Summarize. |
People who liked this also viewed
6 picksType
- find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 2026
- grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026
- vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026
- improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026
- setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026
- triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026
