triage-issues

Classify and label GitHub issues by type, area, platform, and severity.

5|Updated Jul 25, 2025
One-click install
npx skills add https://github.com/tomzx/agents --skill triage-issues-tomzx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage-issues
Source: https://github.com/tomzx/agents/tree/main/skills/triage-issues
Command: npx skills add https://github.com/tomzx/agents --skill triage-issues-tomzx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Triage Issues skill automates the process of classifying and labeling incoming GitHub issues by type, area, platform, provider, severity qualifiers, urgency, and importance, eliminating manual triage drift.

Core Features & Use Cases

  • Classify open issues across multiple dimensions (type, area, platform, provider, severity qualifiers) and determine repro status.
  • Apply repository-specific labels and post clarification comments when information is missing, enabling faster triage and consistent workflows.
  • Detect potential duplicates and optionally surface suggestions or apply duplicate labeling to newer issues while linking to originals.
  • Supports read and write operations via gh CLI, with optional creation of new area labels when confidence is high.

Quick Start

Run the triage-issues workflow against a repository to automatically classify open issues and apply labels.

Frequently Asked Questions about triage-issues

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

FAQPage Schema
How do I automate GitHub issue triage and labeling?

GitHub issue triage is automated by classifying open issues across multiple dimensions like type, area, platform, and severity to apply standardized labels. The workflow uses gh CLI to read context, post clarification comments, and update labels automatically.

How does automated issue classification determine severity and urgency?

Automated issue classification determines severity and urgency by analyzing issue content and reproduction status against repository-specific criteria. It applies these classifications as labels to standardize triage and ensure consistent prioritization.

Do I need the gh CLI to automate issue labeling workflows?

Yes, you need the gh and gh-cached tooling to automate issue labeling workflows. The automation requires access to the repository context via the gh CLI to perform read and write operations for updating labels and posting comments.

Can I detect duplicate GitHub issues automatically?

Yes, you can detect duplicate GitHub issues automatically. The workflow detects potential duplicates and optionally surfaces suggestions or applies duplicate labeling to newer issues while linking them to the original issues.

What is the best way to handle missing information in GitHub issues?

Handling missing information in GitHub issues is managed by posting clarification comments automatically. The triage workflow evaluates issue content for reproduction status and missing details, prompting users for the necessary information to proceed with classification.

Does automated issue triage work with private GitHub repositories?

Yes, automated issue triage works with private GitHub repositories by respecting repository privacy settings. The workflow uses gh CLI access permissions to securely read context, classify issues, and apply labels within the authorized environment.