triage

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

2|Updated May 12, 2026
One-click install
npx skills add https://github.com/tajo9128/BioDockify-Pharma-AI --skill triage-tajo9128
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/tajo9128/BioDockify-Pharma-AI/tree/main/.agents/skills/triage
Command: npx skills add https://github.com/tajo9128/BioDockify-Pharma-AI --skill triage-tajo9128

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintainers lose time manually sorting incoming issues and PRs, verifying bug claims, and writing specifications detailed enough for autonomous agents to execute. This Skill standardizes that workflow with a defined state machine, verification steps, and durable agent briefs. ## Core Features & Use Cases - State machine triage: Categorize issues as bug or enhancement and move them through needs-triage, needs-info, ready-for-agent, ready-for-human, and wontfix states. - Claim verification: Reproduce reported bugs or check out PR diffs and run tests before recommending a state, so briefs are grounded in confirmed behavior. - Agent brief generation: Write durable, behavioral specifications 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 duplicate requests arrive. - Use Case: A maintainer runs triage on a backlog of 30 unlabeled issues; the Skill buckets them, verifies each bug against the codebase, and posts agent-ready briefs for the ones worth delegating. ## 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 workflow in natural language, such as asking what needs attention or naming a specific issue number. The assistant gathers issue context, verifies claims against the codebase, recommends a category and state, and applies labels or comments after your confirmation.

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 items so an autonomous agent can implement the change without further clarification.

Can triage handle pull requests as well as issues?

Yes, external pull requests are treated as issues with attached code and move through the same states. The assistant reads the diff, checks out the PR, and runs relevant tests to confirm the change 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 prior request links. During triage, new issues 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 follows the same structure but notes why delegation is not appropriate.