triage

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintainers drown in unlabeled issues and external PRs that lack clear categorization, verification, and actionable specifications. This Skill moves each item through a defined state machine of triage roles so every issue ends up categorized, verified, and either ready for an agent, ready for a human, or closed with documented reasoning. ## Core Features & Use Cases - State machine triage: Apply category roles (bug, enhancement) and state roles (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix) to issues and external PRs, with conflict detection and maintainer confirmation. - Verification and grilling: Reproduce reported bugs, check out PR diffs to confirm claims, check for redundant existing implementations, and run structured questioning rounds to flesh out vague requests. - Agent briefs and out-of-scope records: Write durable, behavior-focused agent briefs with acceptance criteria, and record rejected enhancements in a .out-of-scope/ knowledge base to deduplicate future requests. - Use Case: A maintainer runs triage on a backlog of 30 unlabeled GitHub issues; each one gets categorized, verified against the codebase, and either receives an agent-ready brief, a needs-info request to the reporter, or a documented wontfix closure. ## 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 it end to end.

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 number. The assistant gathers context, verifies claims against the codebase, recommends a category and state, and applies the outcome after your confirmation.

What labels does an issue triage workflow use?▼

It uses two category roles, bug and enhancement, plus five state roles: needs-triage, needs-info, ready-for-agent, ready-for-human, and wontfix. Every triaged issue carries exactly one of each, and the actual label strings are mapped from your tracker configuration.

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 diff is checked out and verified, and discovery surfaces only external PRs while explicitly named PRs are always triaged regardless of author.

What is an agent brief in issue triage?▼

An agent brief is a structured comment posted when an issue reaches ready-for-agent, describing desired behavior, key interfaces, testable acceptance criteria, and explicit out-of-scope boundaries. It avoids file paths and line numbers so it stays valid as the codebase changes.

When should a rejected feature request be recorded?▼

Rejected enhancements are written to an .out-of-scope/ directory with the decision, reasoning, and links to prior requests, so future duplicates can be surfaced during triage. Bugs and already-implemented requests are never recorded there.