triage-issue

Classifies and labels a single GitHub issue by type, area, platform, provider, and priority.

11|1|Updated Jul 25, 2025

Search Tags:#github #classification #gh cli #priority #duplicate detection #issue triage #labeling

Ready to run

npx skills add https://github.com/tomzx/agents --skill triage-issue-tomzx

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: triage-issue
Source: https://github.com/tomzx/agents/tree/main/skills/triage-issue
Command: npx skills add https://github.com/tomzx/agents --skill triage-issue-tomzx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually reviewing and labeling every incoming GitHub issue is slow and inconsistent, especially in large repositories. This Skill automates per-issue triage by reading an issue, classifying it across multiple dimensions, applying labels, setting issue types and priority, and detecting duplicates. ## Core Features & Use Cases - Multi-dimensional classification: Categorizes issues by type (bug, feature, question, chore, documentation, security), area, platform, provider, severity qualifiers, and reproduction status using the repository's existing label catalog. - Priority and issue type assignment: Maps classification to GitHub Issue Types and org-level Priority fields via GraphQL, with label-based fallbacks. - Duplicate detection and clarification requests: Compares the issue against all open and closed issues to flag duplicates, and posts clarification comments when reports lack sufficient detail. - Use Case: A webhook fires when issue #42 is opened in your repository. Invoke the Skill to automatically label it as a bug in area:ui on platform:ios, set its priority to Urgent, and link it to a potential duplicate. ## Quick Start Ask the agent to triage GitHub issue number 42 in your repository by classifying it and applying the appropriate labels.

Frequently Asked Questions about triage-issue

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

FAQPage Schema

How do I automatically triage a GitHub issue with labels?▼

Invoke the Skill with an issue number and optional owner/repo argument. It reads the issue and comments, classifies it across type, area, platform, and provider dimensions, then applies matching labels discovered from the repository's existing label set.

How does GitHub issue duplicate detection work?▼

The Skill compares the issue against all open and closed issues using signals like similar titles, matching stack traces, and shared reproduction steps, requiring at least two signals to flag. It reports up to five potential duplicates and posts a comment linking to the originals.

Can issue triage run without write permissions on a repository?▼

Yes, the Skill checks push, triage, admin, and maintain permissions first. Without triage access on a public repo it skips labels and priority but still posts duplicate-suggestion and clarification comments; on private repos it outputs a read-only summary.

Does the triage workflow set GitHub Issue Types and priority?▼

Yes, it maps the classified type to the repository's available GitHub Issue Types via the REST API and sets an org-level Priority field through the GraphQL setIssueFieldValue mutation. If no Priority field exists, it falls back to priority labels.

When are urgency and importance labels skipped during triage?▼

Urgency and importance labels are only applied to issues in private repositories. For public repositories, the Skill skips those dimensions and derives priority directly from the issue content instead.