triage

Triage GitHub issues through a state machine of category and state roles.

1|2|Updated Nov 25, 2017
One-click install
npx skills add https://github.com/asarchami/dotfiles --skill triage-asarchami
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/asarchami/dotfiles/tree/main/dot_config/opencode/skills/triage
Command: npx skills add https://github.com/asarchami/dotfiles --skill triage-asarchami

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintainers face a constant stream of incoming bug reports and feature requests that need consistent evaluation, labeling, and preparation before work can begin. This Skill standardizes issue triage by moving each issue through a defined state machine, ensuring nothing falls through the cracks and every issue ends up with clear next steps. ## Core Features & Use Cases - State machine workflow: Assigns one category role (bug or enhancement) and one state role (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix) to every issue, with defined transitions and maintainer override handling. - Bug reproduction and grilling: Attempts to reproduce reported bugs by tracing code and running tests, then asks reporters clarifying questions one at a time when details are missing. - Agent brief generation: Produces durable, behavior-focused agent briefs with testable acceptance criteria for issues delegated to AFK agents, avoiding stale file path or line number references. - Out-of-scope knowledge base: Checks and maintains a persistent record of rejected feature requests so duplicate proposals are caught early. - Use Case: A maintainer runs triage on a new bug report; the Skill reads the issue, attempts reproduction, asks the reporter for missing reproduction steps, and posts structured triage notes until the issue is ready for an agent or human. ## Quick Start Ask the assistant to triage a specific GitHub issue by number and recommend a category and state with reasoning.

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 point it at a specific issue. It reads the full issue and prior triage notes, explores the relevant codebase, then recommends a category (bug or enhancement) and a state such as needs-info or ready-for-agent before applying labels and comments.

What is an agent brief for GitHub issues?

An agent brief is a structured issue comment that serves as the authoritative specification for an AFK agent. It describes current and desired behavior, key interfaces, and testable acceptance criteria while avoiding file paths and line numbers that go stale.

How does automated bug reproduction work during triage?

Before asking the reporter questions, the triage flow reads the reporter's steps, traces the relevant code, and runs tests or commands. It reports whether reproduction succeeded with a code path, failed, or lacked sufficient detail, which signals a needs-info state.

Can triage handle previously rejected feature requests?

Yes. It checks a persistent out-of-scope knowledge base during context gathering and surfaces matches to the maintainer. New entries are written only when an enhancement is rejected as wontfix, with durable reasoning and links to prior requests.

What happens when an issue is missing information from the reporter?

The issue moves to the needs-info state and the assistant posts structured triage notes summarizing what is established and what questions remain. Once the reporter replies, the issue returns to needs-triage for re-evaluation.