triage

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

3|1|Updated May 29, 2026
One-click install
npx skills add https://github.com/mambo-wang/CodingHub --skill triage-mambo-wang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/mambo-wang/CodingHub/tree/main/.codebuddy/skills/triage
Command: npx skills add https://github.com/mambo-wang/CodingHub --skill triage-mambo-wang

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 a category, a state, and a clear next step — including durable briefs that autonomous agents can execute against. ## 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 roles (bug/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 delegation 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, in-progress, and needs-info items with new reporter activity — then picks #42, verifies the bug, and moves it to ready-for-agent with a complete brief. ## 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 with a natural language request like "show me anything that needs my attention" or "let's look at #42". The skill gathers full issue context, verifies claims against the codebase, and 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, describing current behavior, desired behavior, key interfaces, and testable acceptance criteria. It avoids file paths and line numbers so it stays valid as the codebase changes.

Does this triage workflow handle pull requests?▼

Yes, external pull requests are treated as issues with attached code and move through the same states. For PRs, the skill checks out the diff, runs relevant tests to confirm claims, and writes briefs describing remaining work on the existing diff.

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 prior issue 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?▼

Route to ready-for-human when the work requires judgment calls, external access, design decisions, or manual testing that an autonomous agent cannot perform. The brief uses the same structure but notes why delegation is not possible.