Move GitHub issues and external PRs through a triage state machine with agent-ready briefs.
npx skills add https://github.com/Ab0umar/selrs.cc.BU --skill triage-ab0umar
Please help me install this Agent Skill. Skill: triage Source: https://github.com/Ab0umar/selrs.cc.BU/tree/main/.agents/skills/triage Command: npx skills add https://github.com/Ab0umar/selrs.cc.BU --skill triage-ab0umar
.out-of-scope/ files and surfaces prior rejections when similar requests reappear. - Use Case: A maintainer runs triage on Monday morning, sees three buckets of items needing attention, verifies a reported bug, grills an ambiguous feature request into shape, and posts an agent brief so an AFK agent can implement it. ## Quick Start Ask the assistant to show everything on the issue tracker that needs triage attention, or name a specific issue or PR number to evaluate.High-intent search queries and answers about installing and using this skill.
Invoke the triage workflow in natural language, such as asking what needs attention or naming a specific issue number. The assistant reads the full issue, checks the codebase for redundancy and prior rejections, then recommends a category and state before applying labels and comments.
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.
Yes, external PRs are treated as issues with attached code and move through the same states. The assistant additionally reads the diff, checks out the PR, and runs relevant tests to confirm the change does what it claims before recommending a state.
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 matches are surfaced to the maintainer before re-litigating.
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.
phillip-hirschConfigure issue tracker, triage labels, and domain documentation for engineering skills.
noh-rsTurn an in-progress code change into a merge-ready GitHub pull request.
shaahyInterrogates a plan or design through structured questioning while generating ADRs and a glossary.
sortie-aiAutomate GitHub issue creation, editing, searching, triaging, and closing via gh CLI.