triage

Classify issues by category and state with triage context.

32|5|Updated Oct 6, 2024

Search Tags:#automation #workflow #github #prioritization #triage #state-machine #issue-tracker

Ready to run

npx skills add https://github.com/gilesknap/tpi-k3s-ansible --skill triage-gilesknap

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Organize and prioritize incoming issues by applying a structured triage workflow, ensuring consistent labeling and handoffs between teams.

Core Features & Use Cases

State-machine driven triage workflow with defined category and state transitions
Surface context from the issue body, comments, labels, reporter, and prior triage notes to inform decisions
Surface and reference prior out-of-scope decisions to avoid duplicate work
Post an agent brief when the issue is ready for automation, or triage notes for human follow-up

Quick Start

Run a triage pass on a specific issue and generate an agent brief when ready.

Frequently Asked Questions about triage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate GitHub issue triage and prioritization?▼

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.

What states can an issue be assigned during a triage workflow?▼

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.

How does issue triage handle out-of-scope or duplicate feature requests?▼

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.

Can I use a state machine to prepare agent briefs from issue comments?▼

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.

What is the best way to structure human follow-up for complex GitHub issues?▼

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.

Why does my automated issue tracker need a structured triage workflow?▼

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.