triage

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

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/MaksymilianCzadowski/skills --skill triage-maksymilianczadowski
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/MaksymilianCzadowski/skills/tree/main/skills/engineering/triage
Command: npx skills add https://github.com/MaksymilianCzadowski/skills --skill triage-maksymilianczadowski

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintainers drown in unlabeled issues and half-specified requests. This Skill runs a structured triage workflow that categorizes issues and external PRs, verifies claims against the codebase, grills reporters for missing detail, and produces durable agent-ready briefs so work can be delegated to AFK agents or humans. ## Core Features & Use Cases - State machine triage: Applies category roles (bug, enhancement) and state roles (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix) to issues and external PRs, treating a PR as an issue with attached code. - Codebase verification: Reproduces reported bugs, checks out PR diffs to confirm they work, detects already-implemented requests, and checks the .out-of-scope/ knowledge base for prior rejections. - Agent brief generation: Writes durable, behavioral agent briefs with acceptance criteria and explicit scope boundaries, plus needs-info triage notes that preserve grilling progress. - Use Case: A maintainer says "Let's look at #42." The Skill reads the issue, searches the codebase for existing implementations, verifies the bug, grills the reporter for missing detail, then posts an agent brief and moves the issue to ready-for-agent. ## Quick Start Ask the assistant to triage issue number 42 on the repository 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 with a natural-language request like "show me anything that needs my attention" or "let's look at #42". The Skill gathers issue context, checks the codebase for existing implementations, recommends a category and state, and applies labels with your confirmation.

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, testable acceptance criteria, and explicit out-of-scope boundaries so an autonomous coding 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 state machine. The Skill checks out the diff, runs relevant tests to verify claims, and writes briefs describing what remains to be done on the existing code.

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.

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 brief follows the same structure but notes why delegation is not possible.