Triage GitHub issues through a state machine enforcing category and state role rules.
npx skills add https://github.com/shushuzn/Rairos --skill triage-shushuzn
Please help me install this Agent Skill. Skill: triage Source: https://github.com/shushuzn/Rairos/tree/main/skills/triage Command: npx skills add https://github.com/shushuzn/Rairos --skill triage-shushuzn
It helps teams consistently triage GitHub issues by moving them through clearly defined roles and state transitions, so issues do not stall and agent handoff is well-specified.
bug or enhancement and assigns exactly one state role to reflect its current status.AGENT-BRIEF.md when moving an issue to ready-for-agent.Real-world use case: when an incoming issue is vague and lacks reproduction details, the maintainer can move it to needs-info, then re-triage it to ready-for-human or ready-for-agent after new information arrives.
Ask an AI to run /triage and show what issues currently need your attention, grouped into unlabeled, needs-triage, and needs-info.
High-intent search queries and answers about installing and using this skill.
A GitHub issue state machine enforces category and state role rules during triage, ensuring each issue moves through clearly defined states like needs-info or ready-for-agent without stalling. This structured triage maintains consistent status tracking and smooth agent handoff.
To prepare issues for AFK agent execution, triage them to the ready-for-agent state and generate an agent brief using the AGENT-BRIEF.md contract. This durable brief specifies the exact execution context and requirements for the automated agent.
Yes, maintainers can apply quick overrides on issue labels during triage. The state machine respects these manual adjustments while automatically flagging any conflicting labels to prevent invalid state transitions and maintain triage integrity.
Move vague bug reports missing reproduction details to the needs-info state during triage. Once the reporter provides the missing information, you can re-triage the issue to ready-for-human or ready-for-agent for further processing.
Yes, triage-generated comments produced by AI must start with a required AI disclaimer. This policy-based workflow ensures transparency by clearly identifying automated responses on GitHub issues during the categorization and state assignment process.
During triage, the state machine surfaces related out-of-scope decisions by referencing the OUT-OF-SCOPE.md file. This prevents duplicate work on rejected features or bugs by checking new issues against previously documented out-of-scope project boundaries.
rnaarlaAutomate issue triage with state-machine roles and artifact generation.
CarbonTailsAutomates the categorization of issues and pull requests and generates agent briefs.
koseki2580Triage GitHub issues through a state machine with category and state roles.
cloudofgeorgeApply state-machine transitions to triage issues on a tracker.