triage

Assign category and state roles to GitHub issues for consistent routing.

1|Updated May 6, 2026
One-click install
npx skills add https://github.com/ThorStarlord/interface-skills --skill triage-thorstarlord
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/ThorStarlord/interface-skills/tree/main/skills/triage
Command: npx skills add https://github.com/ThorStarlord/interface-skills --skill triage-thorstarlord

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Triage automates moving GitHub issues through a consistent, role-based workflow so problems get evaluated, clarified, delegated, or closed without losing context.

Core Features & Use Cases

  • Issue state machine with canonical roles: Applies exactly one category role (bug or enhancement) and exactly one state role (needs-triage, needs-info, ready-for-agent, ready-for-human, or wontfix).
  • Agent-ready handoff artifacts: Prepares issues for AFK agents by generating durable agent briefs from the current issue context.
  • Durable triage notes and next-step clarity: Produces structured triage notes using a template to avoid re-asking resolved questions.
  • Out-of-scope knowledge base surfacing: Checks the .out-of-scope/ knowledge base and references prior rejections to reduce churn and duplication.

Quick Start

Use the triage skill to move an issue (for example, "#42") into the appropriate state and category by reading its labels, comments, and required context, then posting the correct brief or closing action.

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 with a state machine?▼

Automate GitHub issue triage by assigning exactly one category role and one triage state role to each issue, producing consistent routing outcomes for bugs, enhancements, and agent handoffs. This enforces a canonical state machine workflow.

How do I prepare GitHub issues for an AFK agent?▼

Prepare GitHub issues for AFK agents by generating durable agent briefs from current issue context, applying the ready-for-agent state role, and enforcing triage disclaimers in generated comments.

What is the best way to handle out-of-scope GitHub issues?▼

Handle out-of-scope GitHub issues by checking the .out-of-scope/ knowledge base and referencing prior rejections to reduce churn, applying the wontfix state role to close them consistently.

Can I use workflow automation to route bugs with reproduction attempts to humans?▼

Route bugs with reproduction attempts to humans by applying the ready-for-human triage state role, writing durable triage notes from a template, and ensuring acceptance-criteria-driven workflow transitions are met.

How do I write durable triage notes for GitHub issues?▼

Write durable triage notes for GitHub issues using a structured template to avoid re-asking resolved questions, ensuring next-step clarity and proper context handoff for agents or humans.

Why does issue triage require assigning exactly one category and one state role?▼

Issue triage requires assigning exactly one category role and one state role to prevent conflicting workflow states, ensuring consistent routing outcomes across queues for bugs, enhancements, and agent handoffs.