triage

Automate GitHub issue triage through canonical state machine roles.

1|Updated May 5, 2026
One-click install
npx skills add https://github.com/yashs33244/my-mac-claude --skill triage-yashs33244
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/yashs33244/my-mac-claude/tree/main/skills/mattpocock/engineering/triage
Command: npx skills add https://github.com/yashs33244/my-mac-claude --skill triage-yashs33244

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Triage organizes messy GitHub issues into a clear workflow so bugs and enhancements move quickly to the right next step, with consistent role labels and actionable next actions.

Core Features & Use Cases

  • State-machine issue routing: Moves issues through canonical triage states (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix) using the maintainer’s intent.
  • Durable agent brief generation: Produces contract-style briefs for AFK agents using AGENT-BRIEF.md, including acceptance criteria and scope boundaries.
  • Bug vs enhancement outcomes: Applies different handling for bugs and enhancements, including writing to the .out-of-scope knowledge base for wontfix enhancements.
  • Faster decisions with prior context: Reads the issue body, existing triage notes, and relevant out-of-scope concepts to avoid re-asking resolved questions.

Quick Start

Ask the skill to triage a specific issue number, for example: "Move issue #42 to ready-for-agent."

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 to route bugs and enhancements to the right owner?

Automating GitHub issue triage requires routing bugs and enhancements through a canonical state machine of category and workflow roles, selecting exactly one category and one state role to move issues to the right next step.

How does state machine issue routing work for GitHub bug management?

State machine issue routing works by moving GitHub issues through canonical triage states like needs-triage, needs-info, ready-for-agent, ready-for-human, and wontfix based on maintainer intent and existing triage history.

How do I generate durable agent briefs for AFK agents from GitHub issues?

Generating durable agent briefs for AFK agents involves producing contract-style briefs using AGENT-BRIEF.md, which includes acceptance criteria and scope boundaries extracted from the GitHub issue context.

Does GitHub issue triage handle wontfix outcomes for out-of-scope enhancements?

GitHub issue triage handles wontfix outcomes by applying different handling for bugs and enhancements, specifically writing wontfix enhancement details to the .out-of-scope knowledge base documentation.

What's the best way to avoid re-asking resolved questions during GitHub issue triage?

The best way to avoid re-asking resolved questions is reading the issue body, existing triage notes, and relevant out-of-scope concepts prior to triage to leverage prior context and skip redundant information gathering.

Can I use issue triage to collect missing information before assigning GitHub bugs?

Yes, issue triage applies to bug and enhancement intake by collecting missing information and moving issues to the needs-info state, ensuring all required context is gathered before proceeding to agent or human assignment.