triage-issue

Installation
SKILL.md

Bug investigation -> root cause -> issue file with TDD fix plan. Parallel track to the feature pipeline -- for defects, not capabilities.

Output: ./issues/bugs/<slug>.md

Starting

Accept the bug report -- symptom, error message, repro steps, or just "X is broken."

Before asking anything:

  1. Parse symptom & locate code. Extract what's broken, error messages, affected area. Search for error messages in source, find relevant handlers/components and test files.
  2. Trace the code path. From entry point through to failure. Read each file in the path.
  3. Check history & tests. git log --oneline -20 -- <affected-files> for recent changes. Find test files covering the path -- do they exist? Do they cover the failing case?
  4. Check related work. Search for TODO/FIXME/HACK near affected code. Check ./issues/ for related open work.

Present findings before asking anything:

I've traced the issue. [Symptom] originates in [file] at [function/line]. Recent changes by [commit] modified this path. Here's what I found: [diagnosis].

Installs
5
First Seen
Mar 25, 2026
triage-issue — michaelmerrill/skills