triage

Moves GitHub issues and external PRs through a triage label state machine.

2|Updated Jul 6, 2026
One-click install
npx skills add https://github.com/NAMEWTA/learning-open-code --skill triage-namewta
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/NAMEWTA/learning-open-code/tree/main/translator/open-ai-skills/matt-pocock-skills/skills/engineering/triage
Command: npx skills add https://github.com/NAMEWTA/learning-open-code --skill triage-namewta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintainers of open-source projects drown in untriaged issues and external pull requests, and handing work to autonomous coding agents requires precise, durable specifications that raw issue threads rarely provide. ## Core Features & Use Cases - Label State Machine: Moves issues and PRs through category labels (bug, enhancement) and status labels (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix) with conflict detection. - Claim Verification: Reproduces reported bugs and checks out PR diffs to confirm they do what they claim before any further action. - Agent Briefs: Writes durable, behavior-focused agent briefs with acceptance criteria that survive codebase refactors, plus an .out-of-scope/ knowledge base recording rejected feature requests. - Use Case: A maintainer runs the triage command, sees grouped lists of unlabeled and stale issues, picks issue #42, and gets a verified recommendation plus a ready-to-post agent brief. ## Quick Start Ask the assistant to triage issue #42 and move it to the appropriate status with an agent brief.

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 command with a natural-language request such as showing what needs attention or examining a specific issue number. The skill reads the full issue, verifies claims against the codebase, and suggests category and status labels with reasoning.

What is an agent brief for GitHub issues?▼

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

Does this triage workflow handle pull requests?▼

Yes, external pull requests are treated as issues with code attached, using the same labels and state machine. The skill checks out the diff, runs relevant tests, and writes briefs scoped to finishing or fixing the existing changes.

How are rejected feature requests tracked?▼

Rejected enhancements are recorded as Markdown files in an .out-of-scope/ directory with the decision, rationale, and links to prior requests. During triage these files are checked so duplicate requests surface the earlier rejection instead of restarting debate.

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 posted note follows the agent brief structure but explains why the work cannot be delegated to an autonomous agent.