triage

Automate GitHub issue triage with a state machine for categories and states.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It solves the problem of slow, inconsistent issue handling by giving maintainers a clear, state-based workflow for triaging bugs and enhancements.

Core Features & Use Cases

  • Guided triage state machine: Ensures each issue ends up with exactly one category role (bug/enhancement) and one state role (needs-triage/needs-info/ready-for-agent/ready-for-human/wontfix).
  • Durable agent briefs: Converts validated issues into actionable, contract-style brief comments for AFK agents using durable guidance rather than brittle file/line references.
  • Out-of-scope knowledge reuse: References the persistent .out-of-scope/ knowledge base to deduplicate prior rejected enhancement concepts and link prior reasoning.

Quick Start

Use the /triage command to move an issue like #42 into ready-for-agent with an agent brief or into wontfix (including out-of-scope documentation for enhancements).

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 enhancements?

Automated GitHub issue triage uses a state machine to move bugs and enhancements through states like needs-info, ready-for-agent, or wontfix, ensuring consistent evaluation and clear handling decisions.

What is an AI-driven workflow for managing GitHub issues?

An AI-driven GitHub issue workflow applies a triage state machine to user-reported bugs and enhancement requests, assigning exactly one category and one state role to guide maintainers through evaluation and delegation.

How do I create actionable agent briefs from GitHub issues?

You create actionable agent briefs by converting validated GitHub issues into contract-style brief comments using durable guidance and testable acceptance criteria rather than brittle file or line references.

How can I deduplicate rejected enhancement requests in GitHub?

Deduplicate rejected enhancement requests by referencing a persistent out-of-scope knowledge base that stores prior rejected concepts and links to previous reasoning to maintain consistency.

Does GitHub issue triage work with AFK agents for async task delegation?

Yes, GitHub issue triage supports AFK delegation by generating durable, contract-style agent briefs from validated issues that async agents can execute without needing real-time maintainer input.

When should I mark a GitHub issue as wontfix during triage?

You mark a GitHub issue as wontfix during triage when an enhancement is explicitly rejected, documenting the reasoning in the persistent out-of-scope knowledge base for future deduplication.