Triage GitHub issues through a label-driven state machine with agent briefs.
npx skills add https://github.com/oskrgab/petrodb --skill triage-oskrgab
Please help me install this Agent Skill. Skill: triage Source: https://github.com/oskrgab/petrodb/tree/main/.agents/skills/triage Command: npx skills add https://github.com/oskrgab/petrodb --skill triage-oskrgab
.out-of-scope/ files and surfaces prior rejections when similar issues arrive. - Use Case: A maintainer says "Show me anything that needs my attention" and gets three buckets — unlabeled, needs-triage, and needs-info with new reporter activity — then picks issue #42, gets a reproduction attempt and a category recommendation, and moves it to ready-for-agent with a complete agent brief. ## Quick Start Ask the assistant to triage issue number 42 and recommend a category and state with reasoning.High-intent search queries and answers about installing and using this skill.
Invoke the triage skill with a natural language request like "triage #42" or "show me what needs attention". The skill reads the full issue, explores the codebase, recommends a category and state, and applies labels and comments after your confirmation.
An agent brief is a structured issue comment that serves as the authoritative specification for an AFK coding agent. It describes current and desired behavior, key interfaces, testable acceptance criteria, and explicit out-of-scope boundaries without referencing fragile file paths or line numbers.
Store rejected enhancements as Markdown files in a `.out-of-scope/` directory, one file per concept, with the decision, reasoning, and links to prior requests. During triage, new issues are matched against these files to surface previous rejections before re-litigating them.
Yes, for bug reports the skill attempts reproduction before further questioning by reading the reporter's steps, tracing the relevant code, and running tests or commands. A confirmed reproduction strengthens the agent brief, while insufficient detail signals a needs-info state.
It uses two category roles (bug, enhancement) and five state roles (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix). Every triaged issue carries exactly one of each, and the actual label strings in the tracker are mapped from these canonical names.
OutlineDrivenApply configurable label-based state machines to triage GitHub issues.
NAMEWTAMoves GitHub issues and external PRs through a triage label state machine.
voidcorp-coreWrites a session checkpoint file capturing dead ends, assumptions, and the next action before stopping work.
MultiQCAutomate MultiQC module request triage with priority scoring and GitHub actions.