github-triage

Name: github-triage
Availability: InStock
Author: jupes

Automate GitHub issue triage with a label-based state machine.

2|Updated Apr 11, 2026

Search Tags:#github #issue management #issue triage #state machine #GitHub API

Ready to run

npx skills add https://github.com/jupes/agent-forge-harness --skill github-triage-jupes

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill simplifies the triage process of GitHub issues by providing a label-based state machine, streamlining the workflow for reviewing and categorizing incoming issues.

Core Features & Use Cases

Label-Based State Machine: Automate the categorization of issues based on predefined labels, reducing manual work and improving consistency.
GitHub Integration: Directly interact with GitHub issues using gh commands for reads and writes.
Automated Comments and Labeling: Generate comments and update issue labels based on the state machine rules.
Use Case: When you need to quickly review incoming GitHub issues and categorize them into 'needs-triage', 'ready-for-agent', 'ready-for-human', or 'wontfix' states.

Quick Start

Use the github-triage skill to apply the 'needs-triage' label and a category to a new issue.

Frequently Asked Questions about github-triage

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

FAQPage Schema

How do I automate GitHub issue triage for incoming repository tickets?▼

Automate GitHub issue triage by applying a label-based state machine to categorize incoming tickets into states like needs-triage, ready-for-agent, ready-for-human, or wontfix. This reduces manual review work and improves workflow consistency.

What is a label-based state machine for managing GitHub issues?▼

A label-based state machine uses predefined GitHub labels to automatically categorize and transition issues through triage states. It evaluates current labels to determine the next state, generating comments and updating labels based on defined rules.

Do I need the gh CLI installed to manage GitHub issues with a state machine?▼

Yes, the gh CLI is required to manage GitHub issues with this state machine. It relies on gh commands to interact directly with the GitHub API for reading issues, updating labels, and generating automated comments.

How do I categorize new GitHub issues into ready-for-human or wontfix states?▼

Categorize new GitHub issues by applying predefined labels that trigger the state machine to evaluate rules and assign states like ready-for-human or wontfix. This automated labeling process streamlines the review workflow.

Can I automatically generate comments on GitHub issues during triage?▼

Yes, you can automatically generate comments on GitHub issues during triage. The state machine updates issue labels and posts comments based on the specific categorization rules defined for each triage state.

What are the limitations of using GitHub labels for issue triage state management?▼

Using GitHub labels for issue triage state management requires strict adherence to predefined label schemes. The state machine logic depends entirely on label consistency, so misapplied or custom labels outside the schema may disrupt the automated workflow.