Automate GitHub issue triage by assigning category and state roles.
npx skills add https://github.com/miptah21/skills --skill triage-miptah21
Please help me install this Agent Skill. Skill: triage Source: https://github.com/miptah21/skills/tree/main/.agents/skills/triage Command: npx skills add https://github.com/miptah21/skills --skill triage-miptah21
This Skill solves the problem of inconsistent or slow GitHub issue handling by enforcing a clear triage state machine with durable decision-making artifacts.
It classifies issues into exactly one category role (bug or enhancement) and one state role (needs-triage, needs-info, ready-for-agent, ready-for-human, or wontfix) while guiding the maintainer through gathering context, reproducing bugs when possible, and producing the right follow-up comment type. It supports preparing AFK-agent-ready work by generating structured agent briefs and writing durable out-of-scope records for rejected enhancements.
Use the triage skill to move an issue to the correct workflow label and, if needed, generate an agent brief based on the full issue context.
High-intent search queries and answers about installing and using this skill.
Automating GitHub issue triage uses a state machine to assign exactly one category role and one state role, ensuring consistent workflow routing. It evaluates issue context to select outcomes like ready-for-agent, needs-info, or wontfix.
Preparing GitHub issues for an AFK agent involves generating a structured agent brief from the full issue context. The triage process moves issues to a ready-for-agent state role after gathering context and reproducing bugs when possible.
Issue triage handles out-of-scope enhancement requests by assigning a wontfix state role and writing durable out-of-scope records. It consults reference documents to document the rejection decisions for rejected enhancements.
Yes, you can use a state machine to route bug reports needing more information by assigning a needs-info state role. It reads existing prior triage notes and generates the appropriate follow-up comment type to request missing information.
Documenting bug reproduction steps during GitHub issue triage involves gathering full issue context and attempting to reproduce the bug. The state machine then transitions the issue to a ready-for-human or ready-for-agent state role based on findings.
remiconnessonAssign category and state to GitHub issues using a state-machine workflow.
ayehiaaAssign category and state roles to GitHub issues via a state-machine workflow.
TrebuchetDynamicsOrchestrate GitHub issue triage with role-based state transitions and agent briefs.
hgxszhjEnforce a state-machine workflow for issue triage roles and transitions.
