issue-triage

Converts vague issue reports into structured triage documents with recommended next steps.

Updated Sep 1, 2026
One-click install
npx skills add https://github.com/amirbiron/Han --skill issue-triage-amirbiron
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue-triage
Source: https://github.com/amirbiron/Han/tree/main/han-research/skills/issue-triage
Command: npx skills add https://github.com/amirbiron/Han --skill issue-triage-amirbiron

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Incoming bug reports and issues are often too vague or incomplete to act on, forcing developers to guess what is missing and what to do next. This Skill turns a raw issue or bug report into a structured triage document that names what is known, what is missing, and which follow-up action to take. ## Core Features & Use Cases - Issue Classification: Categorizes each report as Bug, Feature Request, Performance, Security, Regression, Question, or Other before any analysis. - Gap Analysis: Extracts reported and expected behavior, then lists only the information genuinely absent, such as reproduction steps, environment details, or success criteria. - Severity and Reproducibility Assessment: Estimates severity and reproducibility from stated facts, marking them Unknown or omitting them when not inferable. - Next-Step Routing: Recommends the single appropriate follow-up, such as investigate, research, plan-a-feature, plan-implementation, or clarify with the reporter. - Use Case: A teammate pastes a one-line bug report saying the export button stopped working. The Skill classifies it as a Regression, lists missing reproduction steps and environment details, and recommends clarifying with the reporter before investigation. ## Quick Start Ask the assistant to triage this issue report and paste the raw bug report or issue text into the conversation.

Frequently Asked Questions about issue-triage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I triage a vague bug report before investigating?▼

Pass the raw report text or a file path to the issue-triage skill. It classifies the issue type, extracts what is known, lists missing information like reproduction steps or environment details, and recommends whether to investigate, research, plan, or clarify with the reporter.

What information should a good bug report contain?▼

A complete bug report includes reproduction steps, environment details such as OS, browser, and version, error messages or stack traces, and frequency of occurrence. The triage output lists exactly which of these are absent from a given report.

Does issue triage investigate root causes or trace code?▼

No. Issue triage only structures what the reporter wrote and identifies gaps. Root cause analysis, debugging, and code path tracing are handled by the separate investigate skill, which triage may recommend as the next step.

When should I clarify with the reporter instead of investigating?▼

Clarify first when reproduction steps, environment details, or user-impact scope are missing for bugs, regressions, performance, or security issues. The triage report makes this recommendation explicitly when those gaps exist.

Where is the triage report saved?▼

By default the report is written to $HOME/.claude/triages/ with a filename derived from the issue summary. You can also specify a custom output path when invoking the skill.