triage

Triage GitHub issues through a label-driven state machine with agent briefs.

Updated Nov 23, 2024
One-click install
npx skills add https://github.com/tokisakiyuu/dotfiles --skill triage-tokisakiyuu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/tokisakiyuu/dotfiles/tree/main/home/dot_claude/skills/triage
Command: npx skills add https://github.com/tokisakiyuu/dotfiles --skill triage-tokisakiyuu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintainers of open-source or team projects face a constant stream of unstructured bug reports and feature requests. This Skill moves issues through a consistent triage state machine so every issue ends up classified, actionable, and either ready for an AFK agent, ready for a human, waiting on the reporter, or closed with documented reasoning. ## Core Features & Use Cases - State machine triage: Applies one category role (bug or enhancement) and one state role (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix) to every issue, with conflict detection and maintainer confirmation. - Agent brief generation: Writes durable, behavior-focused agent briefs with acceptance criteria and explicit scope boundaries so AFK agents can implement issues weeks later without stale file references. - Out-of-scope knowledge base: Records rejected feature requests in .out-of-scope/ files and surfaces prior rejections when similar requests reappear, preventing re-litigation. - Use Case: A maintainer says "Show me anything that needs my attention" and gets three buckets — unlabeled issues, in-progress triage, and needs-info issues with new reporter activity — then picks one to reproduce, grill, and move to ready-for-agent with a complete brief. ## Quick Start Ask the assistant to triage issue number 42 on the repository and recommend a category and state with reasoning.

Frequently Asked Questions about triage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I triage GitHub issues with an AI assistant?▼

Invoke the triage skill with a natural language request like "triage #42" or "show me anything that needs attention". The skill reads the full issue, explores the codebase, recommends a category and state label, and applies the outcome after your confirmation.

What labels does the triage state machine use?▼

It uses two category roles (bug, enhancement) and five state roles (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix). Every triaged issue carries exactly one of each, and the actual label strings in your tracker can be mapped to these canonical names.

How do I prepare a GitHub issue for an autonomous coding agent?▼

Move the issue to ready-for-agent and post an agent brief comment. The brief describes current and desired behavior, key interfaces, testable acceptance criteria, and explicit out-of-scope items, avoiding file paths and line numbers that go stale.

Can the triage skill handle rejected feature requests?▼

Yes. Rejected enhancements are recorded in .out-of-scope/ markdown files capturing the decision, reasoning, and prior requests. During future triage, matching requests are surfaced so the maintainer can confirm, reconsider, or distinguish them.

What happens when a bug report lacks enough detail to triage?▼

The skill attempts reproduction first by tracing the reporter's steps through the code. If detail is insufficient, it posts structured triage notes listing what is established and specific questions for the reporter, then applies the needs-info label.