issue-triage

Categorize GitHub issues, detect duplicates, and recommend next actions.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/Star1131/smart_insole --skill issue-triage-star1131
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue-triage
Source: https://github.com/Star1131/smart_insole/tree/main/.claude/skills/rtk-master/.claude/skills/issue-triage
Command: npx skills add https://github.com/Star1131/smart_insole --skill issue-triage-star1131

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you rapidly audit a GitHub repository’s open issues, separate signal from noise, and decide what needs attention now versus later.

Core Features & Use Cases

  • Issue Categorization: Classifies issues as bugs, features, enhancements, or questions based on labels, titles, bodies, and context.
  • Duplicate and PR Link Detection: Finds likely duplicates and cross-references open or merged pull requests that already address an issue.
  • Risk and Staleness Review: Flags security-sensitive, breaking-change, and stale issues so you can prioritize safely.
  • Use Case: Run it on a busy repository to produce a clear triage table, draft helpful comments, and recommend labels or closure actions.

Quick Start

Use the issue-triage skill to inspect the repository’s open issues and generate a categorized triage summary with duplicate detection, risk assessment, and recommended next actions.

Frequently Asked Questions about issue-triage

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

FAQPage Schema
How do I triage GitHub issues to find duplicates and stale items?▼

To triage GitHub issues, you can analyze repository metadata to categorize issues, detect duplicates, cross-reference linked pull requests, and flag stale activity for safe prioritization.

What is the best way to assess risk and prioritize open GitHub issues?▼

Risk assessment for open GitHub issues involves analyzing issue metadata to flag security-sensitive and breaking-change signals, allowing repository maintainers to prioritize safely and recommend labels.

How do I categorize GitHub issues into bugs, features, and questions?▼

Categorizing GitHub issues into bugs, features, enhancements, or questions is done by analyzing the labels, titles, bodies, and context of the open issues in a software repository.

Can I detect linked pull requests and recommend closure for resolved GitHub issues?▼

Yes, you can cross-reference open or merged pull requests that address a GitHub issue, enabling you to generate draft comments and recommend safe closure actions for repository maintainers.

Does issue triage work for busy repositories with high open issue volume?▼

Issue triage is designed for busy repositories to rapidly audit open issues, separate signal from noise, and produce a categorized triage summary with actionable next steps for maintainers.