triage

Move GitHub issues and external PRs through a labeled triage state machine.

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

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 to agents or humans. This Skill enforces a structured triage workflow so every issue gets a category, a state, and an actionable outcome. ## 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 rounds 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 runs triage on a backlog of 30 unlabeled issues; the Skill buckets them, verifies each claim against the codebase, and produces ready-for-agent briefs an AFK agent can execute. ## Quick Start Ask the agent 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 agent?▼

Invoke the triage workflow with a natural language request like "show me anything that needs my attention" or "triage #42". The agent reads the issue, verifies claims against the codebase, and recommends a category and state before applying labels.

How to write a good agent brief for GitHub issues?▼

Describe desired behavior and interfaces rather than file paths or line numbers, since code changes over time. Include concrete, independently testable acceptance criteria and explicit out-of-scope boundaries so the agent knows when it is done.

Does this triage workflow handle pull requests?▼

Yes, external PRs are treated as issues with attached code and move through the same states. The agent checks out the diff, runs relevant tests to confirm the PR does what it claims, and writes briefs scoped to finishing the existing change.

What happens to rejected feature requests during triage?▼

Rejected enhancements are recorded in a .out-of-scope/ directory with the decision, reasoning, and links to prior requests. Future matching issues are surfaced against these records so rejections are not 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.