issue-triage

Classify incoming issues, bugs, or requests and recommend the next action. Use when a backlog needs prioritization or issue state needs to be clarified.

SKILL.md

GitHub

Issue Triage

Triage is diagnosis and routing, not a promise to implement. Read the issue and inspect relevant evidence before assigning severity or priority.

For each item, record:

  1. Category: bug, feature, question, docs, security, maintenance, or duplicate.
  2. Reproduction/evidence: observed behavior, expected behavior, environment, and missing information.
  3. Impact: affected users, frequency, severity, blast radius, and workaround.
  4. Confidence: confirmed, likely, or unverified; distinguish user report from reproduced fact.
  5. Disposition: accept, investigate, clarify, duplicate, defer, or close with rationale.
  6. Next action: the smallest useful step, likely owner if known, and blockers.

Use a consistent priority rubric if the project has one; do not invent labels or change tracker state. Keep security reports private and follow the project's disclosure policy. Do not close issues merely because they are difficult or lack an immediate fix.