triage

Moves GitHub issues and external PRs through a triage state machine with agent briefs.

2|Updated Jun 21, 2026
One-click install
npx skills add https://github.com/IsKenKenYa/skills --skill triage-iskenkenya
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/IsKenKenYa/skills/tree/main/skills/engineering/triage
Command: npx skills add https://github.com/IsKenKenYa/skills --skill triage-iskenkenya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintainers drown in unlabeled issues and external PRs with no consistent process for classifying, verifying, and routing them. This Skill enforces a structured triage workflow so every issue gets a category, a state, and—when ready—a durable agent brief that an autonomous agent can execute against. ## Core Features & Use Cases - State machine triage: Routes issues and PRs through canonical roles (bug/enhancement × needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix) with conflict detection. - Verification and grilling: Reproduces reported bugs, checks out PRs to confirm diffs, checks for redundant implementations and prior rejections in .out-of-scope/, then grills vague requests into shape. - Durable agent briefs: Writes behavioral, path-independent briefs with acceptance criteria so AFK agents can execute work weeks later. - Use Case: A maintainer runs /triage on Monday, sees three buckets of items needing attention, picks issue #42, verifies the reported bug, and posts an agent brief that an autonomous coding agent picks up the next day. ## 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 skill and describe what you want in natural language, such as showing items needing attention or examining a specific issue number. The skill reads the issue, verifies claims against the codebase, and recommends a category and state before applying labels.

What is an agent brief for GitHub issues?▼

An agent brief is a structured comment posted when an issue reaches ready-for-agent state. It describes desired behavior, key interfaces, and testable acceptance criteria without referencing file paths or line numbers, so it stays valid as the codebase changes.

Can triage handle external pull requests as well as issues?▼

Yes, when the issue tracker config treats external PRs as a request surface. A PR is triaged as an issue with attached code, using the same roles and states, with the diff checked out and verified during the verification step.

How does the .out-of-scope directory prevent duplicate feature requests?▼

Rejected enhancement requests are recorded as concept files in .out-of-scope/ with the decision, reasoning, and prior issue links. During triage, new issues are matched against these files by concept similarity so prior rejections are surfaced instead of 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.