triage

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

Updated Jul 31, 2026
One-click install
npx skills add https://github.com/julianckt/adoptarun --skill triage-julianckt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/julianckt/adoptarun/tree/main/.agents/skills/triage
Command: npx skills add https://github.com/julianckt/adoptarun --skill triage-julianckt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintainers drown in unlabeled issues and half-specified feature requests. This Skill runs a structured triage workflow that categorizes issues and external PRs, verifies claims against the codebase, grills reporters for missing detail, and produces durable agent-ready briefs so work can be delegated to AFK agents or humans. ## Core Features & Use Cases - State machine triage: Applies category roles (bug, enhancement) and state roles (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix) to issues and external PRs, treating a PR as an issue with attached code. - Codebase verification: Reproduces reported bugs, checks out PR diffs to confirm claims, detects already-implemented requests, and matches new requests against a .out-of-scope/ knowledge base of prior rejections. - Agent brief authoring: Writes durable, behavioral agent briefs with acceptance criteria and explicit scope boundaries, plus structured needs-info triage notes that preserve resolved context. - Use Case: A maintainer says "Let's look at #42" — the Skill reads the issue, checks the codebase for existing implementations and prior rejections, verifies the claim, grills the reporter if needed, and posts an agent brief so an AFK agent can implement it. ## Quick Start Ask the assistant to triage issue #42 or show everything on the issue tracker that needs attention.

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 "show me anything that needs my attention" or "let's look at #42". The Skill reads the issue, checks the codebase for existing implementations, verifies the claim, and recommends a category and state role before applying labels and comments.

What is an agent brief for GitHub issues?

An agent brief is a structured comment posted when an issue moves to ready-for-agent, serving as the authoritative spec for an AFK 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 PRs are treated as issues with attached code and move through the same roles and states. The Skill 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 prior issue links. During triage, new requests are matched against these files by concept similarity so prior rejections are surfaced instead of re-litigated.

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 uses the same structure but notes why delegation is not possible.