issue-triage

Audit GitHub issues and pull requests to categorize, detect duplicates, and assess risk.

75.3k|4.7k|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/rtk-ai/rtk --skill issue-triage-rtk-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-triage
Source: https://github.com/rtk-ai/rtk/tree/main/.claude/skills/issue-triage
Command: npx skills add https://github.com/rtk-ai/rtk --skill issue-triage-rtk-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the tedious process of triaging GitHub issues, ensuring that open issues are categorized, duplicates are detected, and relevant information is surfaced, leading to a more organized and efficient development workflow.

Core Features & Use Cases

  • Automated Auditing: Scans open issues and PRs to identify bugs, feature requests, and potential duplicates.
  • Risk Assessment: Classifies issues based on potential security risks or breaking changes.
  • Duplicate Detection: Compares titles and bodies to flag potential duplicate issues.
  • Staleness Detection: Identifies issues that haven't been updated in a long time.
  • Comment Drafting: Generates draft comments for further action or information requests.
  • Use Case: When a repository accumulates many open issues, this Skill can perform an initial audit, categorize them, flag duplicates, and identify stale issues, allowing maintainers to focus on critical items.

Quick Start

Run the issue-triage skill to audit all open issues in the current repository.

Frequently Asked Questions about issue-triage

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

FAQPage Schema
How do I automate triaging GitHub issues to categorize bugs and features?

Automating GitHub issue triage involves auditing open issues and pull requests to categorize them into bug, feature, or enhancement types. An automated Skill can analyze titles and bodies to detect duplicates, assess risk levels, and identify stale issues.

What is the best way to detect duplicate GitHub issues?

Detecting duplicate GitHub issues is done by comparing the titles and bodies of open issues. Automated triage tools analyze this text content to flag potential duplicates, allowing maintainers to consolidate similar reports and streamline repository management.

Can I cross-reference open GitHub pull requests with existing issues?

Cross-referencing open GitHub pull requests with existing issues is supported during the deep analysis phase. The triage process audits both issues and PRs to identify links, assess potential breaking changes, and surface relevant information for maintainers.

Do I need GitHub CLI authentication to audit open issues?

GitHub CLI authentication is required to audit open issues and pull requests. The automated triage process operates in phases including data gathering, deep analysis, and validated action execution, all of which depend on authenticated GitHub CLI access to interact with your repository.

How do I identify stale GitHub issues that need attention?

Identifying stale GitHub issues is part of the automated triage auditing process. The Skill scans open issues to detect those that haven't been updated in a long time, allowing maintainers to focus on critical items and draft comments for further information requests.

Can automated triage assess security risks in GitHub issues?

Automated triage assesses security risks by classifying GitHub issues based on potential security vulnerabilities or breaking changes. During the deep analysis phase, the Skill evaluates issue content to help maintainers prioritize critical bugs and high-risk feature requests.