triage

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

Updated Sep 13, 2026
One-click install
npx skills add https://github.com/U1traVeno/skills --skill triage-u1traveno
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/U1traVeno/skills/tree/main/profiles/matt/triage
Command: npx skills add https://github.com/U1traVeno/skills --skill triage-u1traveno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintainers drown in unlabeled issues and external PRs with no consistent process for evaluating, categorizing, and preparing work for implementation. This Skill enforces a structured triage workflow that turns raw reports into verified, fully specified work items. ## Core Features & Use Cases - State machine triage: Move issues and PRs through category roles (bug, enhancement) and state roles (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix) with conflict detection. - Verification and grilling: Reproduce reported bugs, check out PR diffs to confirm claims, and run structured questioning rounds to flesh out vague requests before assignment. - Agent brief generation: Write durable, behavior-focused agent briefs with acceptance criteria and scope boundaries that survive codebase changes. - Out-of-scope knowledge base: Record rejected feature requests in .out-of-scope/ files and surface prior rejections when duplicate requests arrive. - Use Case: A maintainer runs triage on Monday morning, sees three unlabeled issues and one external PR, verifies a reported bug, grills an ambiguous feature request into shape, and posts an agent brief so an AFK agent can implement it. ## Quick Start Ask the assistant to show everything on the issue tracker that needs triage attention, or name a specific issue or PR number to triage.

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 and describe what you want in natural language, such as showing items needing attention or naming a specific issue. The assistant gathers context, verifies claims against the codebase, 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 reaches ready-for-agent state, serving as the authoritative specification for an autonomous coding agent. It describes desired behavior, key interfaces, testable acceptance criteria, and explicit out-of-scope boundaries without referencing fragile file paths or line numbers.

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

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

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 requests. 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 cannot be reproduced?▼

The assistant attempts to reproduce the bug from the reporter's steps and reports the result as confirmed, failed, or insufficient detail. Insufficient detail is a strong signal to apply the needs-info state and post triage notes with specific questions for the reporter.