triage

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

Updated May 28, 2026
One-click install
npx skills add https://github.com/changfengpro/agent-skills --skill triage-changfengpro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/changfengpro/agent-skills/tree/main/skills/triage
Command: npx skills add https://github.com/changfengpro/agent-skills --skill triage-changfengpro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintainers lose track of incoming issues and PRs, and under-specified tickets waste agent and human time. This Skill runs a consistent triage workflow that categorizes, verifies, grills, and converts issues into actionable work items. ## 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. - Verification and grilling: Reproduces reported bugs, checks out PR diffs to confirm claims, and runs structured questioning to flesh out vague requests. - Agent briefs and out-of-scope records: Writes durable, behavior-focused agent briefs for delegation and maintains a .out-of-scope/ knowledge base of rejected feature requests. - Use Case: A maintainer asks what needs attention, reviews an unlabeled bug report, verifies the reproduction, and moves it to ready-for-agent with a complete brief an AFK agent can execute. ## Quick Start Ask the assistant to triage issue #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 workflow with a natural language request like "show me anything that needs attention" or "triage #42". The assistant gathers context, verifies claims, 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, testable acceptance criteria, and explicit out-of-scope boundaries so an autonomous agent can implement it.

Can triage handle pull requests as well as issues?

Yes, external PRs are treated as issues with attached code and move through the same states. The assistant checks out the diff, runs relevant tests to confirm the PR's claims, and writes briefs describing remaining work on the existing diff.

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

Rejected enhancements are recorded as concept files in .out-of-scope/ with the decision, reasoning, and prior request links. During triage, new issues are matched against these files by concept similarity so prior rejections are surfaced before re-litigating.

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.