triage

Classifies GitHub issues into roles and states using a rule-based workflow.

13|3|Updated May 12, 2026
One-click install
npx skills add https://github.com/kevinnft/ai-agent-skills --skill triage-kevinnft
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/kevinnft/ai-agent-skills/tree/main/skills/mattpocock/engineering/triage
Command: npx skills add https://github.com/kevinnft/ai-agent-skills --skill triage-kevinnft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triage and organize project issues by applying a structured, role-based state machine to drive issue workflow.

Core Features & Use Cases

  • Canonical roles for categories (e.g., bug, enhancement) and states (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix) to standardize triage.
  • Guidance documents integration via AGENT-BRIEF.md and OUT-OF-SCOPE.md to surface decisions and scope boundaries.
  • Interactive invocation via /triage to classify issues, gather context, and apply the appropriate state and category.

Quick Start

Describe the triage request and invoke /triage to begin the workflow.

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

Automate GitHub issue triage by applying a role-based state machine that moves issues through defined lifecycle states like needs-triage, needs-info, and wontfix. This standardizes issue workflow management by classifying items and applying appropriate states.

What's the best way to organize unlabeled GitHub issues for bugs and enhancements?

Organize unlabeled GitHub issues by invoking a structured triage workflow that classifies items into canonical categories like bug or enhancement. The workflow then applies states such as ready-for-agent or ready-for-human to guide subsequent handling.

Can I use a stateful workflow to move issues from needs-triage to ready-for-human?

Yes, a stateful workflow moves issues from needs-triage to ready-for-human by applying a small state machine driven by defined triage roles. This structured approach ensures issues transition correctly through their lifecycle states.

How do I document scope boundaries when managing GitHub issue states?

Document scope boundaries when managing GitHub issue states using integrated reference docs like AGENT-BRIEF.md and OUT-OF-SCOPE.md. These guidance files surface triage decisions and define what falls outside the workflow's processing scope.

Does GitHub issue triage automation work without external dependencies?

Yes, GitHub issue triage automation works without external dependencies by running a self-contained state machine workflow. It requires no additional packages to classify issues, gather context, and apply appropriate states and categories.

When should I assign wontfix status during issue triage?

Assign wontfix status during issue triage when an issue falls outside project scope as defined by OUT-OF-SCOPE.md guidelines. The stateful workflow applies this status as a terminal state to formally close unsuitable requests.