issue-triage

Audit GitHub issues via gh CLI and draft validated triage actions.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/Alamator/code-ultimate --skill issue-triage-alamator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-triage
Source: https://github.com/Alamator/code-ultimate/tree/main/examples/skills/issue-triage
Command: npx skills add https://github.com/Alamator/code-ultimate --skill issue-triage-alamator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual burden of sorting, analyzing, and acting on a repository's open issues by performing a structured audit, detecting duplicates, classifying risk and staleness, and drafting validated GitHub actions for maintainers to approve.

Core Features & Use Cases

  • Automated Audit: Gather open and recent closed issues and PRs via the gh CLI and produce triage tables (critical, PR-linked, active, duplicates, stale).
  • Duplicate Detection: Compute local Jaccard similarity on normalized title+body to flag potential duplicates and recommend consolidation.
  • Deep Analysis & Parallel Agents: Optionally launch per-issue analysis agents to verify categories, identify missing info, estimate fix effort, and produce exact comment text.
  • Validated Actions: Draft comments, label additions, and close actions using templates and require explicit user validation before executing any gh commands.
  • Use Cases: backlog cleanup, stale issue closing, duplicate consolidation, and prioritized security/regression escalation.

Quick Start

Run /issue-triage all to audit all open issues, optionally analyze selected issues in depth, and generate draft comments, labels, and close actions for your approval.

Frequently Asked Questions about issue-triage

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

FAQPage Schema
How do I automate GitHub issue triage and backlog cleanup?

Automate GitHub issue triage by auditing open issues via the gh CLI, classifying categories and risk, detecting duplicates with Jaccard similarity, and drafting validated actions for your approval before execution.

How does duplicate detection work for GitHub issues?

Duplicate detection for GitHub issues works by computing local Jaccard similarity on normalized issue titles and bodies to flag potential duplicates and recommend consolidation.

Can I use gh CLI to automatically close stale issues and add labels?

Yes, you can use gh CLI to draft comments, label additions, and close actions for stale issues, but the workflow requires explicit human validation before executing any gh commands.

Does automated issue triage protect high-risk or collaborator-authored issues?

Automated issue triage explicitly protects collaborator-authored or high-risk issues by staging human validation before any comments, labels, or closures are applied.

What is the best way to consolidate duplicate GitHub issues?

The best way to consolidate duplicate GitHub issues is to compute Jaccard similarity on normalized text to flag duplicates, classify categories, and draft consolidation actions for maintainer approval.

How do I audit open GitHub issues for security and regression risks?

Audit open GitHub issues by gathering data via gh CLI, classifying risk and staleness, identifying PR cross-references, and prioritizing security and regression escalation for validated action.