triage

Move GitHub issues and external PRs through a triage state machine with agent-ready briefs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintainers drown in unlabeled issues and external PRs that lack clear categorization, verification, and actionable specifications. This Skill structures the entire triage workflow so every issue ends up with a clear category, state, and either a durable agent brief or a documented rejection. ## Core Features & Use Cases - State machine triage: Move issues and PRs through needs-triage, needs-info, ready-for-agent, ready-for-human, and wontfix states with bug or enhancement categories. - Verification and grilling: Reproduce reported bugs, check out PR diffs to confirm claims, and run structured questioning rounds before writing specifications. - Agent briefs and out-of-scope knowledge base: Write durable, behavior-focused agent briefs for AFK agents and record rejected feature requests in .out-of-scope/ files to deduplicate future requests. - Use Case: A maintainer asks what needs attention, reviews an unlabeled bug report, verifies the reproduction, grills the reporter for missing details, then posts an agent brief and moves the issue to ready-for-agent. ## Quick Start Ask the assistant to show anything on the issue tracker that needs triage attention, or to triage a specific issue number.

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 workflow in natural language, such as asking what needs attention or naming a specific issue number. The assistant gathers context, verifies claims against the codebase, recommends a category and state, and applies labels with comments after your confirmation.

What is an agent brief for GitHub issues?▼

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

Can triage handle external pull requests as well as issues?▼

Yes, external PRs are treated as issues with attached code and move through the same states. The assistant additionally checks out the diff and runs relevant tests to confirm the PR does what it claims before recommending a state.

How does the out-of-scope knowledge base prevent duplicate feature requests?▼

Rejected enhancements are recorded as concept files in a .out-of-scope/ directory with the decision, reasoning, and prior request links. During triage, new issues are matched against these files by concept similarity so prior rejections surface instead of being re-litigated.

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

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