triage

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

Updated Sep 20, 2024
One-click install
npx skills add https://github.com/AnasIsmai1/dotfiles --skill triage-anasismai1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/AnasIsmai1/dotfiles/tree/main/agents/.agents/skills/triage
Command: npx skills add https://github.com/AnasIsmai1/dotfiles --skill triage-anasismai1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintainers drown in unlabeled issues and external PRs with no consistent process for categorizing, verifying, and routing work. This Skill enforces a structured triage state machine so every issue gets exactly one category and one state, with durable agent briefs for delegable work. ## Core Features & Use Cases - State machine triage: Routes issues and PRs through needs-triage, needs-info, ready-for-agent, ready-for-human, and wontfix states with category labels (bug or enhancement). - Verification and grilling: Reproduces reported bugs, checks out PR diffs to confirm claims, and runs structured questioning to flesh out vague requests before routing. - Agent briefs and out-of-scope memory: Writes durable, behavior-focused agent briefs for delegable work and maintains a .out-of-scope/ knowledge base to deduplicate rejected feature requests. - Use Case: A maintainer says "Show me anything that needs my attention" and gets three buckets — unlabeled, needs-triage, and needs-info with new reporter activity — then picks #42, verifies the bug, and posts an agent brief moving it to ready-for-agent. ## Quick Start Ask the assistant to triage issue #42 on the repository's issue tracker and recommend a category and state.

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 "Let's look at #42" or "Show me anything that needs my attention". The skill reads the full issue, checks the codebase for existing implementations and prior rejections, then recommends a category and state before applying labels and comments.

What is an agent brief for GitHub issues?▼

An agent brief is a structured comment posted when an issue moves to ready-for-agent, serving as the authoritative spec for an autonomous coding agent. It describes desired behavior, key interfaces, testable acceptance criteria, and explicit out-of-scope boundaries without referencing file paths or line numbers.

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

Yes, when the issue tracker config treats external PRs as a request surface, a PR is triaged as an issue with attached code using the same roles and states. The skill additionally checks out the diff and runs relevant tests to verify the PR does what it claims.

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

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

When should an issue go to ready-for-human instead of ready-for-agent?▼

Use ready-for-human when the work requires judgment calls, external access, design decisions, or manual testing that an autonomous agent cannot perform. The skill posts the same brief structure but notes why the work cannot be delegated.