triage

Categorize issues into canonical roles and states via a state-machine workflow.

2|1|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/huangzida/skills --skill triage-huangzida
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/huangzida/skills/tree/main/triage
Command: npx skills add https://github.com/huangzida/skills --skill triage-huangzida

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triage issues in project trackers can be slow and inconsistent. This Skill standardizes triage by enforcing a compact, state-machine driven workflow and by guiding the creation of durable agent briefs.

Core Features & Use Cases

  • Canonical roles: exactly one category role (bug or enhancement) and one state role (needs-triage, needs-info, ready-for-agent, ready-for-human, or wontfix) per issue.
  • Agent-brief integration: surfaces a ready-to-use AGENT-BRIEF.md as triage results are prepared for AFK agents.
  • End-to-end triage flow: gather context, make a recommendation, optionally reproduce the bug, grill for missing data, and apply the outcome while updating notes and out-of-scope references.
  • Out-of-scope surface: reads .out-of-scope/*.md to surface prior rejections during triage.

Quick Start

Describe the issue and run the triage protocol to determine its category and state.

Frequently Asked Questions about triage

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

FAQPage Schema
How do I automate issue triage for bugs and enhancements in my workflow?

A state-machine-driven triage workflow categorizes issues by assigning exactly one category (bug or enhancement) and one state (needs-triage, needs-info, ready-for-agent, ready-for-human, or wontfix) per issue. This standardizes the process and positions issues for agents or humans.

What is the best way to prepare issues for automated agents in issue tracking?

Preparing issues for autonomous agents involves creating durable agent briefs like AGENT-BRIEF.md during triage. The workflow grills for missing data, optionally reproduces bugs, and sets the state to ready-for-agent, ensuring AFK agents receive complete context.

How does a state machine workflow handle issue categorization and missing information?

A state machine workflow handles issue categorization by enforcing canonical roles and transitioning issues to a needs-info state when data is missing. It gathers context, optionally reproduces bugs, and grills for missing data before applying the final triage outcome.

Does the triage workflow support referencing previously rejected issues?

The triage workflow supports referencing previously rejected issues by reading markdown files from the .out-of-scope directory. This surfaces prior rejections during the triage process to maintain consistency and prevent duplicate efforts.

What are the limitations of enforcing one category and one state per issue?

Enforcing one category and one state per issue limits categorization to strictly bug or enhancement roles, preventing multi-tagging. This constraint ensures clear positioning for agent briefs but may require separate tracking for complex issues spanning multiple categories.