triage

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

Updated Sep 11, 2026
One-click install
npx skills add https://github.com/CYRUS-pinto/pi-bot --skill triage-cyrus-pinto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/CYRUS-pinto/pi-bot/tree/main/.agents/skills/triage
Command: npx skills add https://github.com/CYRUS-pinto/pi-bot --skill triage-cyrus-pinto

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, moving items through a consistent state machine so nothing falls through the cracks and every actionable item ends with a clear, durable brief. ## 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. - Claim verification: Reproduce reported bugs or check out PR diffs and run tests to confirm claims before investing in specification work. - Agent brief generation: Write durable, behavioral agent briefs with acceptance criteria and scope boundaries that survive codebase changes. - Out-of-scope knowledge base: Record rejected feature requests in .out-of-scope/ files and surface prior rejections when similar requests arrive. - Use Case: A maintainer runs triage on Monday morning, sees three unlabeled issues and one external PR, verifies a reported bug, grills an ambiguous feature request into shape, and closes a duplicate dark-mode request by linking the existing out-of-scope record. ## 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 directly.

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 to see anything needing attention or naming a specific issue number. The assistant gathers context, recommends a category and state, verifies claims against the codebase, and applies labels with explanatory 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, serving as the authoritative specification for an autonomous coding agent. It describes 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 roles and states. The workflow 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 enhancements 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, and matches are surfaced to the maintainer before re-litigating.

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 brief uses the same structure as an agent brief but notes why the work cannot be delegated to an autonomous agent.