triage

Categorize and route GitHub issues through a defined state machine.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the chaos of unmanaged issue trackers by enforcing a structured state machine for bugs and feature requests, ensuring that every issue is clearly defined and actionable.

Core Features & Use Cases

  • State Machine Management: Automatically routes issues through defined roles like needs-triage, ready-for-agent, and wontfix.
  • Agent Brief Generation: Creates durable, high-quality specifications for AFK agents to execute without needing constant human guidance.
  • Institutional Memory: Maintains an out-of-scope knowledge base to prevent re-litigating previously rejected feature requests.

Quick Start

Invoke the triage skill to review all unlabeled issues and recommend the next 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 automate GitHub issue triage for bugs and feature requests?

Automating GitHub issue triage involves applying a state machine to categorize and prioritize bugs and enhancements. This skill routes issues through defined roles like needs-triage and ready-for-agent to ensure every issue is actionable.

What is the best way to generate agent briefs from GitHub issues?

Generating agent briefs from GitHub issues requires creating durable, high-quality specifications for AFK agents. This allows automated agents to execute tasks without needing constant human guidance during the issue lifecycle.

How do I manage out-of-scope feature requests in GitHub issue trackers?

Managing out-of-scope feature requests in GitHub issue trackers is done by maintaining an institutional memory knowledge base. This prevents re-litigating previously rejected feature requests by documenting wontfix states and rejection rationale.

Do I need specific GitHub labels to automate issue tracking workflows?

Yes, automating issue tracking workflows requires integration with project-specific labels. The triage state machine relies on these defined labels to properly categorize issues and adhere to defined triage roles and state transition logic.

How does a state machine help with unmanaged issue trackers?

A state machine helps unmanaged issue trackers by enforcing a structured lifecycle for bugs and feature requests. This ensures that every issue is clearly defined, categorized, and routed to the correct state for agent handoffs.

Can I use this triage skill to review all unlabeled issues at once?

Yes, you can invoke the triage skill to review all unlabeled issues and recommend the next state for each one. This applies the state machine logic to automatically route issues through defined roles like needs-triage and ready-for-agent.