github-triage

Apply configurable label-based state machines to triage GitHub issues.

5|2|Updated Nov 17, 2025

Search Tags:#automation #workflow #github #issues #triage #labeling #state-machine

Ready to run

npx skills add https://github.com/OutlineDriven/odin-gemini-cli-extension --skill github-triage-outlinedriven

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: github-triage
Source: https://github.com/OutlineDriven/odin-gemini-cli-extension/tree/main/skills/github-triage
Command: npx skills add https://github.com/OutlineDriven/odin-gemini-cli-extension --skill github-triage-outlinedriven

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triage GitHub issues using a configurable label-based state machine to route issues through standard workflow stages and prepare them for autonomous agents or human review. The repo is inferred from git remote; all GitHub calls go through gh.

Core Features & Use Cases

Stateful label-based triage with a map from abstract state tokens to repo-specific labels.
Support for automating transitions to agent-ready or human-ready states, plus easy human overrides.
Invariants and governance: exactly one category and one state label per issue to ensure consistent state tracking.
Use Case: a maintainer triages incoming issues in a project, enabling automated preparation for autonomous agents or manual review.

Quick Start

Start triaging a newly opened issue by applying the default category and state labels and generating a concise triage summary.

Frequently Asked Questions about github-triage

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

FAQPage Schema

How do I automate triage for incoming GitHub issues?▼

Automate GitHub issue triage by applying a configurable label-based state machine to route incoming issues through standard workflow stages for autonomous agents or human review. The system enforces exactly one state label per issue.

What is a label-based state machine for GitHub issue triage?▼

A label-based state machine for GitHub issue triage maps abstract state tokens to repository-specific labels to enforce consistent state tracking. This maintains governance by requiring exactly one category label and one state label per issue.

How do I enforce consistent state tracking across GitHub issues and PRs?▼

Enforce consistent state tracking by applying a configurable category and state label map to incoming issues and PRs. This approach guarantees invariants by requiring exactly one category label and one state label per issue.

Can I use gh CLI to automate GitHub issue labeling workflows?▼

Yes, you can use gh CLI to automate GitHub issue labeling workflows. The triage system infers the repository from the git remote and routes all GitHub interactions directly through the gh command line tool.

Does this triage workflow support preparing issues for autonomous agents?▼

Yes, this triage workflow supports preparing issues for autonomous agents. It automates transitions to agent-ready or human-ready states and provides easy human overrides using a configurable label-based state machine.

What are the limitations of using label-based triage for GitHub issues?▼

A limitation of label-based triage is the strict invariant requiring exactly one category and one state label per issue. You must configure a category and state label map beforehand, and all interactions are restricted to the gh CLI.