Move GitHub issues and external PRs through a triage state machine with agent-ready briefs.
npx skills add https://github.com/filippolmt/skills --skill triage-filippolmt
Please help me install this Agent Skill. Skill: triage Source: https://github.com/filippolmt/skills/tree/main/skills/triage Command: npx skills add https://github.com/filippolmt/skills --skill triage-filippolmt
needs-triage, needs-info, ready-for-agent, ready-for-human, and wontfix states with category roles (bug / enhancement). - Verification and grilling: Reproduce reported bugs, check out PR diffs to confirm claims, and run grilling sessions to flesh out vague requests before routing them. - Agent briefs and out-of-scope tracking: Write durable, behavior-focused agent briefs for delegation, and maintain a .out-of-scope/ knowledge base that deduplicates rejected feature requests. - Use Case: A maintainer runs triage on a backlog of 30 unlabeled GitHub issues; the Skill buckets them, verifies each claim against the codebase, and produces agent-ready briefs for the ones worth building. ## Quick Start Ask the assistant to show everything on the issue tracker that needs triage attention, then pick an issue to evaluate.High-intent search queries and answers about installing and using this skill.
Invoke the triage workflow and describe what you want in natural language, such as showing items needing attention or examining a specific issue number. The assistant gathers context, verifies claims against the codebase, and recommends a category and state before applying labels and comments.
An agent brief is a structured comment posted when an issue moves to ready-for-agent, serving as the authoritative spec for an autonomous coding agent. It describes desired behavior, key interfaces, acceptance criteria, and explicit scope boundaries without referencing fragile file paths or line numbers.
Yes, external PRs are treated as issues with attached code and move through the same states. The assistant checks out the diff, runs relevant tests to confirm the PR does what it claims, and writes briefs describing what remains to finish it.
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 surface instead of being re-litigated.
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.
nkabbaraAutomate issue tracker, triage labels, and domain documentation setup.
FoxSilouImplement backend features autonomously from feature descriptions or .feature files.
mikalvRuns a structured design interview that produces ADRs and a glossary.
OutlineDrivenApply configurable label-based state machines to triage GitHub issues.