Classify issues by category and state with triage context.
npx skills add https://github.com/gilesknap/tpi-k3s-ansible --skill triage-gilesknap
Please help me install this Agent Skill. Skill: triage Source: https://github.com/gilesknap/tpi-k3s-ansible/tree/main/.claude/skills/triage Command: npx skills add https://github.com/gilesknap/tpi-k3s-ansible --skill triage-gilesknap
Organize and prioritize incoming issues by applying a structured triage workflow, ensuring consistent labeling and handoffs between teams.
Run a triage pass on a specific issue and generate an agent brief when ready.
High-intent search queries and answers about installing and using this skill.
Automate GitHub issue triage by using a guided state machine to classify incoming issues by category and state. This workflow evaluates issue bodies, comments, and labels to drive consistent prioritization and generate agent briefs or structured notes for human follow-up.
During a triage workflow, issues are classified into states including needs-triage, needs-info, ready-for-agent, ready-for-human, or wontfix. The state machine also categorizes issues as bugs or enhancements to route them to the correct automation or human handler.
Issue triage surfaces and references prior out-of-scope decisions stored in .out-of-scope references to avoid duplicate work. By checking existing triage notes and labels, the workflow identifies previously rejected enhancements and marks them as wontfix.
Yes, a state machine can extract context from issue comments, labels, and reporter information to prepare agent briefs. When an issue reaches the ready-for-agent state, the workflow generates a brief to drive downstream automation.
The best way to structure human follow-up is to generate structured triage notes with clear next steps. When an issue is classified as ready-for-human, the workflow compiles context from the issue body and comments to guide manual resolution.
An automated issue tracker needs a structured triage workflow to ensure consistent labeling and organized handoffs between teams. Applying a state machine to issue prioritization prevents unresolved tickets and streamlines the transition from incoming report to actionable task.
ClyptAITriage GitHub issues using a label-based state machine to assign next actions.
ThorStarlordAssign category and state roles to GitHub issues for consistent routing.
kos3nzApply category and state roles to triage GitHub issues through a standardized workflow.
JohnRobert-OlanoAutomates issue triage in tracker projects using predefined roles and states.
