issue-triage

Classify issue text into a structured triage report with severity and next steps.

198|19|Updated May 7, 2026
One-click install
npx skills add https://github.com/testdouble/han --skill issue-triage-testdouble
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-triage
Source: https://github.com/testdouble/han/tree/main/han-core/skills/issue-triage
Command: npx skills add https://github.com/testdouble/han --skill issue-triage-testdouble

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triages incoming issue reports into a structured, decision-ready summary that identifies type, known facts, missing information, severity, suspected areas, and a recommended next step, enabling faster, more reliable planning.

Core Features & Use Cases

  • Classify issue type (Bug, Regression, Performance, Security, Question, Feature Request, Other) to guide triage routing.
  • Extract and organize what is known, what is missing, reproduction steps, environment details, and suspected areas for investigation.
  • Produce a handoff-ready triage report that feeds subsequent Han skills to resolve the issue.

Quick Start

Provide the issue text or path to an issue report file to begin triage.

Frequently Asked Questions about issue-triage

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

FAQPage Schema
How do I triage incoming issue reports to identify root cause and severity?

To triage an issue report, you provide plain text or a file path so the Skill can classify the type, extract known facts, identify missing information, assign severity, and recommend a next step.

What is the best way to structure a bug report for handoff to a planning workflow?

Structuring a bug report for handoff involves organizing known facts, reproduction steps, environment details, and suspected areas into a decision-ready summary that routes directly to the appropriate follow-on resolution skills.

Can I triage issues from a file without manually adding unstated assumptions?

Yes, you can triage issues from a file without adding unstated assumptions, because the Skill reads project context files to infer relevant areas while strictly avoiding assumptions not present in the original report.

Does issue triage work with plain text reports or do I need a specific format?

Issue triage works directly with plain text or file-based reports, requiring no specific format to extract environment details, reproduction steps, and missing information to produce a structured triage output.

What issue types can be classified during the triage process?

The triage process classifies issue types into Bug, Regression, Performance, Security, Question, Feature Request, or Other to guide routing and plan the appropriate fix.

When should I not use an automated issue triage approach?

You should not use automated issue triage when the report lacks sufficient context for extracting known facts, as the process avoids adding unstated assumptions and relies on provided text and project context files.