triage

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

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

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 them. This Skill enforces a structured triage workflow so every issue gets a category, a state, and either an actionable brief or a clear reason for closure. ## Core Features & Use Cases - State machine triage: Move issues and PRs through needs-triage, needs-info, ready-for-agent, ready-for-human, and wontfix states with bug/enhancement categories. - Verification and grilling: Reproduce reported bugs, validate PR diffs, and ask targeted clarifying questions before committing to a state. - Agent brief generation: Write durable, behavior-focused agent briefs with acceptance criteria that survive codebase changes. - Out-of-scope knowledge base: Record rejected feature requests in .out-of-scope/ files and surface prior rejections when similar requests arrive. - Use Case: A maintainer runs triage on Monday morning, sees three unlabeled issues and one external PR, verifies a reported bug, requests reproduction steps on another, and publishes an agent brief for a well-specified enhancement. ## 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 in natural language, such as asking what needs attention or naming a specific issue number. 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 moves to ready-for-agent. It describes desired behavior, key interfaces, testable acceptance criteria, and explicit out-of-scope boundaries so an autonomous 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 states. The assistant additionally checks out the diff and runs relevant tests to confirm the PR does what it claims before recommending a state.

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

Rejected enhancements are recorded as concept files in the .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 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 uses the same structure but notes why delegation is not appropriate.