triage

Triage GitHub issues through a label-driven state machine with agent briefs.

Updated May 23, 2026
One-click install
npx skills add https://github.com/Oatse/CWE-Automation --skill triage-oatse
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/Oatse/CWE-Automation/tree/main/.agents/skills/triage
Command: npx skills add https://github.com/Oatse/CWE-Automation --skill triage-oatse

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintainers of active repositories face a constant stream of incoming bug reports and feature requests that need consistent classification, reproduction, and specification before work can begin. This Skill moves issues through a structured triage state machine so every issue ends up with a clear category, state, and actionable specification. ## Core Features & Use Cases - State machine triage: Moves issues through canonical roles (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix) with exactly one category (bug or enhancement) and one state per issue. - Agent brief generation: Writes durable, behavior-focused agent briefs with acceptance criteria so AFK agents can implement issues without re-reading stale context. - Out-of-scope knowledge base: Records rejected feature requests in .out-of-scope/ files and surfaces prior rejections when similar requests reappear. - Use Case: A maintainer runs triage on Monday morning, sees three unlabeled issues, reproduces one bug, grills the reporter on another, and moves a well-specified enhancement to ready-for-agent with a complete agent brief. ## Quick Start Ask the assistant to triage issue number 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 assistant?

Invoke the triage skill and describe what you want in natural language, such as showing issues needing attention or examining a specific issue number. The skill reads the full issue, recommends a category and state, and applies labels after your confirmation.

What is an agent brief for GitHub issues?

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

How does the out-of-scope directory work for rejected features?

Rejected enhancement requests are recorded as markdown files in a .out-of-scope/ directory, one file per concept, with the decision, reasoning, and links to prior requests. During triage, new issues are matched against these files to surface previous rejections.

Can I override the triage state machine for a specific issue?

Yes, maintainers can directly command a state change such as moving an issue to ready-for-agent, and the skill applies it after confirming the role changes, comments, and closures. Unusual transitions are flagged for confirmation before proceeding.

When should an issue go to ready-for-human instead of ready-for-agent?

Issues requiring judgment calls, external access, design decisions, or manual testing go to ready-for-human. The skill posts the same structured brief as an agent brief but notes why the work cannot be delegated to an autonomous agent.