triage

Automate issue state transitions across GitHub Issues, Linear, and custom trackers.

40|9|Updated Jan 4, 2026

Search Tags:#automation #workflow #governance #issues #triage #issue-tracking #state-machine

Ready to run

npx skills add https://github.com/akillness/jeo-skills --skill triage-akillness

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/akillness/jeo-skills/tree/main/.agent-skills/triage
Command: npx skills add https://github.com/akillness/jeo-skills --skill triage-akillness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triage issues through a disciplined state machine, turning chaotic backlog items into an orderly, auditable workflow across teams.

Core Features & Use Cases

Enforces standardized transitions between issue states (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix) to align teams and reduce delays.
Auto-labels and routes issues based on category and required information, increasing triage throughput and consistency.
Use Case: A product team receives hundreds of incoming issues; apply the state machine to triage, gather missing details, and assign next actions automatically.

Quick Start

Show the current triage status of open issues and apply the defined state transitions to move items forward.

Frequently Asked Questions about triage

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

FAQPage Schema

How do I automate issue triage for a high-volume product backlog?▼

Automate issue triage by applying a disciplined state machine that routes incoming items through standardized states like needs-triage, needs-info, and ready-for-agent. This enforces consistent transitions, gathers missing details, and assigns next actions automatically to reduce backlog chaos.

Can I use this issue-tracking state machine workflow with GitHub Issues and Linear?▼

Yes, this issue-tracking state machine workflow applies to diverse trackers including GitHub Issues, Linear, and custom trackers. It enforces deterministic transitions and role-based states across these platforms to maintain an orderly, auditable workflow.

What standardized states should an issue triage workflow include?▼

An issue triage workflow should include standardized states such as needs-triage, needs-info, ready-for-agent, ready-for-human, and wontfix. These role-based states enforce clear transitions and ensure auditable decisions from initial categorization through to resolution.

How does automated issue routing handle missing information during triage?▼

Automated issue routing handles missing information by moving items to a needs-info state and auto-labeling them based on category requirements. This structured information gathering ensures all required details are collected before an issue transitions to ready-for-human or ready-for-agent.

What is the best way to enforce auditable decisions in issue tracking?▼

The best way to enforce auditable decisions in issue tracking is implementing a deterministic state machine with role-based states and clear transitions. This structured flow turns chaotic backlog items into an orderly workflow, ensuring every triage decision is recorded and validated.

When should I avoid using a state machine for issue triage?▼

You should avoid using a state machine for issue triage if your team requires highly flexible, ad-hoc workflows without standardized transitions. This approach enforces deterministic routes and strict state categories, which may constrain processes that rely on unstructured issue management.