Categorize and prioritize issue tracker items using state machine transitions.
npx skills add https://github.com/tanglg/cms --skill triage-tanglg
Please help me install this Agent Skill. Skill: triage Source: https://github.com/tanglg/cms/tree/main/.codex/skills/triage Command: npx skills add https://github.com/tanglg/cms --skill triage-tanglg
The triage Skill addresses the challenge of efficiently managing issue tracking by automating the initial categorization and prioritization of issues, reducing the workload on maintainers and ensuring issues are handled promptly.
Use the triage skill to triage an issue and move it to 'ready-for-agent' by running the command: /triage move #42 ready-for-agent.
High-intent search queries and answers about installing and using this skill.
Automating issue triage uses a state machine-driven process to categorize and prioritize issues, reducing manual workload. It automatically transitions issues through states like 'needs-triage' and 'ready-for-agent' to ensure they are handled promptly.
A state machine-driven approach for issue tracking automates transitions between predefined states such as 'needs-info', 'wontfix', and 'ready-for-agent'. It processes issue context to determine the correct state role, like 'bug' or 'enhancement', minimizing manual intervention.
You can use natural language commands to interact with issue tracking and move items between states. For example, maintainers can instruct the system to 'Move #42 to ready-for-agent' or ask it to show issues needing attention.
Automated issue triage supports role-based management by categorizing issues into roles such as 'bug' and 'enhancement'. This role classification combined with state transitions ensures proper routing and prioritization within the tracker.
To transition an issue to ready-for-agent, you execute a triage command specifying the issue number and target state. Running a command like '/triage move #42 ready-for-agent' immediately updates the issue tracking status.
Using a state machine for issue triage requires predefined states like 'needs-info' and 'wontfix', meaning transitions are limited to configured paths. It relies on natural language processing logic, so ambiguous issue descriptions may hinder accurate categorization.
JohnRobert-OlanoAutomates issue triage in tracker projects using predefined roles and states.
statsclawScan, triage, and resolve open GitHub issues with automated pull requests.
ricardoalt1515Categorize issues and pull requests into bug or enhancement states.
henrycashe26Categorize and route GitHub issues through a defined state machine.
