triage

Triage GitHub issues through a state machine with category and state roles.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you quickly triage GitHub issues by moving them through a clear state machine with consistent, role-based decisions and required evidence.

Core Features & Use Cases

  • State-machine triage on demand: Guides how to classify issues into category and state roles (bug vs enhancement; needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix).
  • Durable agent brief creation: Produces an authoritative agent brief contract when issues are ready for AFK work, using durable acceptance criteria and clear scope boundaries.
  • Reproduction-first workflow (bugs only): Requests reproduction steps, runs relevant checks, and escalates to needs-info when details are insufficient.
  • Out-of-scope handling for enhancements: Writes and links to .out-of-scope records for wontfix enhancement decisions to support institutional memory and deduplication.

Quick Start

Use the triage skill by running /triage and describing the issue(s) you want evaluated or moved (e.g., “Show me anything that needs my attention” or “Move #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 with a state machine?

Automated GitHub issue triage uses a defined state machine to classify items into category and state roles, requiring reproduction steps for bugs and delegating ready items to AFK agents.

What is an agent brief contract for AFK delegation?

An agent brief contract is a durable artifact produced during triage that defines acceptance criteria and scope boundaries before assigning issues to AFK agents for autonomous work.

How do I handle out-of-scope enhancement requests on GitHub?

Out-of-scope enhancement requests are handled by marking them wontfix and writing linked .out-of-scope records to maintain institutional memory and prevent duplicate issues.

Can I move unlabeled GitHub issues to ready-for-human automatically?

Unlabeled GitHub issues can be moved to ready-for-human by assigning category and state roles through the triage state machine after evaluating available details and routing.

Why does issue triage require a fixed AI disclaimer?

Issue triage requires a fixed AI disclaimer at the start of outputs to satisfy contract requirements, ensuring transparent communication when AI guides state transitions and artifact generation.

When should I escalate a bug to needs-info status?

A bug should escalate to needs-info status during reproduction-first triage when the provided details are insufficient to run relevant checks or reproduce the reported defect.