triage

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

28|1|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/NauelG/astro-blocks --skill triage-nauelg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/NauelG/astro-blocks/tree/main/.agents/skills/triage
Command: npx skills add https://github.com/NauelG/astro-blocks --skill triage-nauelg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintainers drown in unlabeled issues and external PRs with no consistent process for categorizing, verifying, and routing them. This Skill enforces a structured triage workflow so every issue ends up with a clear category, state, and actionable specification. ## Core Features & Use Cases - State machine triage: Move issues and PRs through needs-triage, needs-info, ready-for-agent, ready-for-human, and wontfix states with category roles (bug or enhancement). - Verification and grilling: Reproduce reported bugs, check out PR diffs to confirm claims, and ask targeted questions to flesh out vague requests. - Agent brief generation: Write 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: 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, verifies one bug by reproducing it, moves it to ready-for-agent with a complete brief, and closes a duplicate feature request by linking to an existing out-of-scope record. ## Quick Start Ask the assistant to show everything on the issue tracker that needs triage attention, then pick an issue to evaluate.

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 skill and describe what you want in natural language, such as showing items needing attention or examining a specific issue number. The skill 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. It describes current and desired behavior, key interfaces, testable acceptance criteria, and explicit out-of-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 using the same roles and states. The skill checks out the diff, runs relevant tests to confirm the PR does what it claims, and writes briefs describing what remains to finish or fix the contribution.

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 prior rejections are surfaced to the maintainer.

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 appropriate.