triage

Triage GitHub issues through a label-driven state machine with agent briefs.

Updated Jul 17, 2026
One-click install
npx skills add https://github.com/unnxt30/skills --skill triage-unnxt30
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/unnxt30/skills/tree/main/triage
Command: npx skills add https://github.com/unnxt30/skills --skill triage-unnxt30

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintainers drown in untriaged issues: bugs without reproductions, feature requests without scope decisions, and issues that stall waiting for reporter info. This Skill moves issues through a structured state machine so every issue gets a category, a state, and a clear next step. ## Core Features & Use Cases - State machine triage: Classifies issues as bug or enhancement and moves them through needs-triage, needs-info, ready-for-agent, ready-for-human, or wontfix states. - Agent brief generation: Writes durable, behavior-focused agent briefs with acceptance criteria so AFK agents can implement issues without re-reading stale context. - Out-of-scope knowledge base: Records rejected feature requests in .out-of-scope/ files and surfaces prior rejections when similar requests reappear. - Use Case: A maintainer runs triage on Monday morning, sees three unlabeled issues, reproduces one bug, requests info on another, and converts a well-specified feature request into an agent brief ready for autonomous implementation. ## Quick Start Ask the assistant to show all issues that need triage attention and recommend a category and state for each one.

Frequently Asked Questions about triage

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

FAQPage Schema
How do I triage GitHub issues with an AI assistant?

Invoke the triage skill and describe what you want in natural language, such as showing issues needing attention or moving a specific issue to a state. The skill reads the full issue, recommends a category and state, and applies labels after your confirmation.

What is an agent brief for GitHub issues?

An agent brief is a structured issue comment that serves as the specification for an autonomous coding agent. It describes current and desired behavior, key interfaces, testable acceptance criteria, and explicit out-of-scope boundaries without referencing fragile file paths or line numbers.

How does the skill handle rejected feature requests?

Rejected enhancements are recorded in an .out-of-scope/ directory with the decision, reasoning, and links to prior requests. During future triage, the skill checks these files and surfaces matches so duplicate requests are not re-litigated.

Can I override the triage state machine manually?

Yes, maintainers can issue direct commands like moving an issue to ready-for-agent, and the skill applies the change after confirming the action. It skips grilling for quick overrides but asks whether you want an agent brief written.

What happens when a bug report lacks reproduction steps?

The skill attempts reproduction first by tracing code and running tests. If detail is insufficient, it posts triage notes listing what is established and specific actionable questions for the reporter, then applies the needs-info state.