Automate GitHub issue triage with role-based state labels and AGENT-BRIEF.md specs.
npx skills add https://github.com/anukkrit149/anukkrit-skills --skill triage-anukkrit149
Please help me install this Agent Skill. Skill: triage Source: https://github.com/anukkrit149/anukkrit-skills/tree/main/cloud/skills/triage Command: npx skills add https://github.com/anukkrit149/anukkrit-skills --skill triage-anukkrit149
This Skill helps you quickly and consistently move GitHub issues through the right triage state so maintainers and AFK agents can act with clear, durable context.
.out-of-scope/ knowledge base and links to it from triage output using OUT-OF-SCOPE.md.Use the /triage instruction to list what needs your attention and recommend category/state label moves for the issues you select.
High-intent search queries and answers about installing and using this skill.
Automating GitHub issue triage involves moving issues through a role-based state machine that assigns consistent category and state labels. This process evaluates bugs and enhancements, prepares issues for AFK agents, and manages wontfix or needs-info followups.
Preparing GitHub issues for agents requires producing durable AGENT-BRIEF.md style specs driven by acceptance criteria. This ensures autonomous agents receive clear, durable context and actionable instructions extracted from the original issue context.
Role-based label management for bug triage works by assigning exactly one category role and one state role to each issue. This maintains workflow consistency across needs-triage, needs-info, ready-for-agent, ready-for-human, and wontfix states.
Yes, you trigger automated issue triage by using the /triage instruction. This lists issues needing attention and recommends category and state label moves for the specific issues you select for evaluation.
Handling wontfix enhancements involves capturing the out-of-scope reasoning in a knowledge base and linking to it from the triage output. This records decision context using OUT-OF-SCOPE.md to maintain a durable history of rejected enhancements.
Yes, you can track needs-info followups by assigning the needs-info state role during issue triage. This maintains consistent workflow states for issues requiring additional information before they can be processed.
dformosoAutomate GitHub issue triage using labels and a predefined state machine.
shushuznTriage GitHub issues through a state machine enforcing category and state role rules.
proffesor-for-testingAutomate GitHub issue triage, board synchronization, and sprint planning.
henrycashe26Categorize and route GitHub issues through a defined state machine.