triage

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

1|Updated Mar 2, 2025
One-click install
npx skills add https://github.com/marjorg/setup --skill triage-marjorg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/marjorg/setup/tree/main/home/.agents/skills/archive/0-matt/triage
Command: npx skills add https://github.com/marjorg/setup --skill triage-marjorg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintainers drown in unlabeled issues and external PRs with no consistent process for evaluating, categorizing, and preparing work for implementation. This Skill enforces a structured triage workflow that turns raw reports into verified, agent-ready specifications. ## Core Features & Use Cases - State machine triage: Move issues and PRs through category roles (bug, enhancement) and state roles (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix) with conflict detection. - Verification and grilling: Reproduce reported bugs, check out PR diffs to confirm claims, and run structured questioning rounds to flesh out vague requests before assignment. - Agent briefs and out-of-scope tracking: Write durable, behavior-focused agent briefs for delegation and maintain a .out-of-scope/ knowledge base that records rejected feature requests to prevent re-litigation. - Use Case: A maintainer runs triage on a backlog of 30 unlabeled issues; the Skill buckets them by attention needed, verifies each bug against the codebase, and produces agent-ready briefs for the ones approved for work. ## Quick Start Ask the assistant to show everything on the issue tracker that needs triage attention, or name a specific issue or PR number to triage it end to end.

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 in natural language, such as asking what needs attention or naming a specific issue number. The assistant gathers full issue context, verifies claims against the codebase, recommends a category and state, and applies labels with structured comments.

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, testable acceptance criteria, and explicit scope boundaries so an autonomous agent can implement the change without further clarification.

Can triage handle external pull requests as well as issues?

Yes, external PRs are treated as issues with attached code and move through the same states. The assistant checks out the diff, runs relevant tests to confirm the PR does what it claims, and writes briefs describing remaining work on the existing diff.

How does the out-of-scope knowledge base prevent duplicate feature requests?

Rejected enhancements are recorded as concept files in a .out-of-scope/ directory with the decision, reasoning, and prior request links. During triage, new issues are matched against these files by concept similarity so prior rejections surface before re-litigation.

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.