triage

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

Updated Apr 16, 2025
One-click install
npx skills add https://github.com/damoke012/eks_code --skill triage-damoke012
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/damoke012/eks_code/tree/main/.claude-env/skills/triage
Command: npx skills add https://github.com/damoke012/eks_code --skill triage-damoke012

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintainers lose time manually evaluating incoming issues and PRs, deciding what is actionable, and writing specifications detailed enough for autonomous agents to execute. This Skill standardizes that workflow with a consistent state machine and durable brief format. ## 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. - Verification and grilling: Reproduce reported bugs, validate PR diffs, and ask structured 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 deduplicate future requests against them. - Use Case: A maintainer runs triage on a backlog of 20 unlabeled issues; the Skill buckets them, verifies each claim against the codebase, and produces ready-for-agent briefs for the actionable ones. ## Quick Start Ask the assistant to show everything on the issue tracker that needs triage attention, or to triage a specific issue number.

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 examining a specific issue number. The assistant gathers context, verifies claims against the codebase, recommends a category and state, and applies labels with your approval.

How do I write a good agent brief for a coding agent?▼

Describe behavioral contracts and acceptance criteria rather than file paths or line numbers, since briefs must stay valid as the codebase changes. Include current behavior, desired behavior, key interfaces, testable acceptance criteria, and explicit out-of-scope boundaries.

Can triage handle pull requests as well as issues?▼

Yes, external pull requests are treated as issues with attached code and move through the same state machine. The assistant additionally checks out the diff and runs relevant tests to confirm the PR does what it claims before recommending a state.

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 issues matching a rejected concept are surfaced to the maintainer instead of being re-litigated from scratch.

When should an issue go to ready-for-agent versus ready-for-human?▼

Issues with fully specified, testable acceptance criteria go to ready-for-agent for autonomous execution. Issues requiring judgment calls, external access, design decisions, or manual testing go to ready-for-human with a note explaining why delegation is not possible.