Categorize GitHub issues and assign state roles for routing.
npx skills add https://github.com/kileroppo/AI-Coding-Guidance-Skills --skill triage-kileroppo
Please help me install this Agent Skill. Skill: triage Source: https://github.com/kileroppo/AI-Coding-Guidance-Skills/tree/main/skills/triage Command: npx skills add https://github.com/kileroppo/AI-Coding-Guidance-Skills --skill triage-kileroppo
This Skill helps maintainers efficiently route GitHub issues through a clear triage workflow, reducing unanswered questions and speeding up delivery by ensuring the right issues reach the right owners.
bug or enhancement, assigns exactly one state role, and moves issues through transitions like needs-triage, needs-info, ready-for-agent, ready-for-human, or wontfix..out-of-scope/ knowledge base for prior rejections and routes new enhancement requests appropriately, including writing/annotating .out-of-scope/ entries when wontfix is decided.bug or enhancement, gather missing details, and prepare a ready-for-agent brief if it’s sufficiently specified.Ask the maintainer to run triage for a specific issue number, for example: "Triaged issue #42—decide the category and move it to ready-for-agent if it is ready, otherwise request the missing information."
High-intent search queries and answers about installing and using this skill.
Automating GitHub issue triage involves categorizing issues as bug or enhancement, assigning a state role like needs-info or ready-for-agent, and moving them through a state-machine workflow to route them to the correct owner or AFK agent for resolution.
To prepare a GitHub issue for an automated agent, you generate a durable agent brief that specifies acceptance criteria and scope boundaries, ensuring the issue is fully scoped and assigned the ready-for-agent state role before handoff.
The .out-of-scope knowledge base provides institutional memory by storing prior enhancement rejections. When a new request arrives, the triage workflow checks this knowledge base to route it appropriately or annotates a new entry when a wontfix decision is made.
Yes, the triage workflow enforces canonical role naming by ensuring exactly one category, either bug or enhancement, and exactly one state role, such as needs-triage, needs-info, ready-for-agent, ready-for-human, or wontfix, is assigned to each issue.
Yes, the triage workflow requires adding a specific triage disclaimer to all generated comments posted on GitHub issues, ensuring transparency that the categorization and state role assignment were produced by an automated process.
Using a state machine for bug reporting and enhancement scoping reduces unanswered questions and speeds up delivery by applying consistent transitions like needs-triage to ready-for-agent, ensuring issues reach the right owners without manual sorting errors.
mmartinsolivOrganize GitHub issues into triage states and next actions.
vessuxClassify project issues into categories and states for triage workflows.
yashs33244Automate GitHub issue triage through canonical state machine roles.
henrycashe26Categorize and route GitHub issues through a defined state machine.