triage

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

Updated Jul 23, 2025
One-click install
npx skills add https://github.com/derrik-fleming/dotfiles --skill triage-derrik-fleming
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/derrik-fleming/dotfiles/tree/main/private_dot_agents/skills/triage
Command: npx skills add https://github.com/derrik-fleming/dotfiles --skill triage-derrik-fleming

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintainers of open-source or team projects struggle to keep incoming bug reports and feature requests organized, evaluated, and ready for implementation. This Skill moves issues through a structured triage state machine so every issue gets a category, a state, and a clear next action. ## Core Features & Use Cases - State machine triage: Assigns each issue one category role (bug or enhancement) and one state role (needs-triage, needs-info, ready-for-agent, ready-for-human, or wontfix). - Agent brief generation: Writes durable, behavior-focused agent briefs so issues marked ready-for-agent can be picked up by an AFK coding agent without further clarification. - Out-of-scope knowledge base: Records rejected feature requests in .out-of-scope/ files and surfaces prior rejections when similar requests reappear. - Use Case: A maintainer runs the triage command, sees all unlabeled and needs-triage issues, picks one, and gets a category recommendation, a reproduction attempt for bugs, and a posted agent brief or needs-info comment. ## Quick Start Ask the assistant to triage issue number 42 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 command and describe what you want in natural language, such as showing issues needing attention or triaging a specific issue number. The assistant reads the full issue, recommends a category and state, and applies labels with your approval.

What is an agent brief for GitHub issues?▼

An agent brief is a structured comment posted when an issue moves to ready-for-agent. It describes current and desired behavior, key interfaces, acceptance criteria, and scope boundaries so an autonomous coding agent can implement the change without further clarification.

How does the out-of-scope knowledge base work?▼

Rejected feature requests are recorded as markdown files in a .out-of-scope/ directory, one file per concept. During triage, new issues are matched against these files by concept similarity so prior rejections are surfaced instead of re-litigated.

Can I override the triage state machine directly?▼

Yes. Telling the assistant to move an issue to a specific state like ready-for-agent applies the role directly without grilling. The assistant confirms the role changes, comments, and closures before acting.

What happens when a bug report lacks enough detail?▼

The issue moves to needs-info and the assistant posts triage notes listing what has been established and specific questions for the reporter. When the reporter replies, the issue returns to needs-triage for re-evaluation.