ticket-triage

Classify GitHub issues by type, severity, and domain using gh CLI.

12|2|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/jikig-ai/soleur --skill ticket-triage-jikig-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ticket-triage
Source: https://github.com/jikig-ai/soleur/tree/main/.openhands/skills/ticket-triage
Command: npx skills add https://github.com/jikig-ai/soleur --skill ticket-triage-jikig-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub issue triage automates classification and routing by severity and domain, reducing manual triage workload and enabling faster response times.

Core Features & Use Cases

  • Classify issues by type (bug, feature request, question, documentation) and severity (P1, P2, P3).
  • Route issues to the appropriate Soleur department (Engineering, Product, Support, etc.) for faster handling.
  • Produce a structured triage report suitable for inline review and auditing.

Quick Start

Provide a concise triage decision for open issues using gh CLI and route each to the correct department.

Frequently Asked Questions about ticket-triage

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

FAQPage Schema
How do I auto-triage GitHub issues by severity and domain?▼

Auto-triage classifies GitHub issues by type, severity, and domain, routing them to departments like Engineering or Product. It uses gh CLI for read-only access and outputs a structured triage report without modifying or closing the original issues.

Can I route GitHub issues to different departments automatically?▼

Yes, you can route GitHub issues automatically. The triage process classifies issues by type and severity, directing them to appropriate departments such as Engineering, Product, or Support to reduce manual workload and enable faster response times.

Does this issue triage workflow modify or close my GitHub tickets?▼

No, the issue triage workflow does not modify or close GitHub tickets. It uses gh CLI for read-only access to evaluate open issues and generates a structured triage report suitable for inline review and auditing.

What is the best way to classify open-source GitHub issues for prioritization?▼

The best way to classify open-source GitHub issues for prioritization is using an automated triage system. It categorizes incoming issues into types like bugs or feature requests and severity levels like P1, P2, or P3, producing a structured report for auditing.

Do I need gh CLI to classify GitHub issues by type and severity?▼

Yes, you need gh CLI installed to classify GitHub issues by type and severity. The triage process relies on gh CLI for read-only access to fetch open issues from both open-source and private repositories before generating the triage report.