github-issue-triage

Categorize, rank, and recommend actions for GitHub issues.

15|1|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/monoes/monomind --skill github-issue-triage-monoes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-issue-triage
Source: https://github.com/monoes/monomind/tree/main/.claude/skills/github-issue-triage
Command: npx skills add https://github.com/monoes/monomind --skill github-issue-triage-monoes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns noisy GitHub issue backlogs into a structured triage workflow, helping you quickly identify priority bugs, duplicates, stale tickets, and issues that need more information.

Core Features & Use Cases

  • Automatic issue audit: Categorizes issues, checks labels, estimates age, flags risk, and recommends next actions.
  • PR and duplicate analysis: Cross-references open pull requests, compares issue titles and bodies, and surfaces likely duplicates.
  • Deep analysis and safe execution: Supports opt-in detailed review of selected issues, drafts comments and labels, and requires explicit approval before any GitHub actions are performed.
  • Use case: A maintainer can review an overflowing repository, identify what needs immediate attention, and prepare consistent follow-up messages without manually scanning every ticket.

Quick Start

Ask the assistant to run the github-issue-triage workflow for the repository issues you want audited, analyzed, and prepared for review.

Frequently Asked Questions about github-issue-triage

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

FAQPage Schema
How do I triage GitHub issues to find priority bugs and duplicates?

To triage GitHub issues, this workflow categorizes open tickets, checks labels, flags risks, and cross-references pull requests to surface priority bugs and likely duplicates. It estimates ticket age and recommends next actions for repository maintenance.

How do I detect stale GitHub issues in an overflowing repository backlog?

Detecting stale GitHub issues involves auditing ticket age and categorizing open issues to identify tickets needing immediate attention. The workflow ranks issues by staleness, checks existing labels, and flags risks to help maintainers prioritize follow-up actions.

Do I need GitHub CLI access to run issue triage workflows?

Yes, you need GitHub CLI access to run this issue triage workflow. The process requires issue and PR metadata fetched via the CLI to categorize tickets, detect duplicates, and prepare draft comments before explicitly validating any actions.

Can I automatically close duplicate GitHub issues without manual approval?

No, you cannot automatically close duplicate GitHub issues without manual approval. The workflow requires explicit validation before executing any comments, labels, or closures, ensuring safe and guided actions for repository maintenance.

What is the best way to cross-reference open pull requests with related GitHub issues?

The best way to cross-reference open pull requests with GitHub issues is using an automated triage workflow that compares issue metadata against PR data. This process surfaces linked tickets and identifies relationships without manually scanning every entry.