triage

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

10|3|Updated Jul 18, 2019
One-click install
npx skills add https://github.com/tanqimin/MyFavsORM --skill triage-tanqimin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/tanqimin/MyFavsORM/tree/main/.agents/skills/triage
Command: npx skills add https://github.com/tanqimin/MyFavsORM --skill triage-tanqimin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintainers of open-source projects face a constant stream of incoming issues and external pull requests that need categorization, verification, and specification before work can begin. This Skill automates the triage workflow so every issue ends up with a clear category, a defined state, and either an actionable brief or a documented rejection. ## Core Features & Use Cases - State machine triage: Moves issues and PRs through canonical roles (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix) with category labels (bug, enhancement). - Verification and grilling: Reproduces reported bugs, checks out PR diffs to confirm claims, and asks targeted questions to flesh out vague requests. - Agent brief generation: Writes durable, behavior-focused agent briefs with acceptance criteria so AFK agents can implement changes without re-reading the whole thread. - 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 and one external PR, verifies a reported bug, sends one issue back for more info, and publishes an agent brief for a confirmed enhancement. ## Quick Start Ask the assistant to show everything on the issue tracker that needs triage attention, or name a specific issue 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 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.

What is an agent brief for GitHub issues?

An agent brief is a structured comment posted when an issue reaches ready-for-agent state, serving as the authoritative specification for an autonomous coding agent. It describes current and desired behavior, key interfaces, testable acceptance criteria, and explicit out-of-scope boundaries without referencing fragile file paths or line numbers.

Can triage handle external pull requests as well as issues?

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

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

Rejected enhancement requests are recorded as concept files in a .out-of-scope/ directory with the decision, reasoning, and links to prior requests. During triage, new issues are matched against these files by concept similarity so prior rejections can be surfaced instead of re-litigated.

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

Issues go to ready-for-human when the work requires judgment calls, external access, design decisions, or manual testing that an autonomous agent cannot perform. The brief uses the same structure but notes why delegation is not appropriate.