skills.rest
amadeus-dlc
amadeus-dlcOFFICIAL
Explore all skills by this author →
GitHub

gh-issue-organizer

Classify, group, and prioritize open GitHub issues for backlog triage.

5|Updated Jun 24, 2026
Search Tags:#github#prioritization#backlog#issues#classification#duplication#triage
One-click install
npx skills add https://github.com/amadeus-dlc/amadeus --skill gh-issue-organizer-amadeus-dlc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gh-issue-organizer
Source: https://github.com/amadeus-dlc/amadeus/tree/main/.agents/skills/gh-issue-organizer
Command: npx skills add https://github.com/amadeus-dlc/amadeus --skill gh-issue-organizer-amadeus-dlc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a crowded GitHub issue backlog into an organized, actionable queue by identifying what is open, what is duplicated, what is stale, and what is ready to close.

Core Features & Use Cases

  • Inventory and classify issues: Separates CodeRabbit-generated issues from manual reports and sorts them into bug, feature, epic, refactoring, or other categories.
  • Group by root cause: Clusters related issues by shared code area or underlying problem so batch fixes become easier to plan and execute.
  • Verify close candidates: Checks the current codebase before recommending closure, helping avoid false closes and surfacing only well-supported results.
  • Prioritize follow-up work: Summarizes remaining issues by urgency so teams can focus on safety, correctness, and high-impact improvements first.

Quick Start

Ask the gh-issue-organizer skill to review the repository's open GitHub issues and produce a categorized triage report with close candidates, groupings, and priorities.

Frequently Asked Questions about gh-issue-organizer

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

FAQPage Schema
How do I triage a crowded GitHub backlog and prioritize open issues?▼

GitHub issue triage works by taking an inventory of open tickets, separating manual reports from automated ones, and grouping them by shared code area or underlying problem. This root-cause grouping helps teams plan and execute batch fixes more efficiently.

What is the best way to clean up duplicate and stale GitHub issues?▼

Cleaning up duplicate and stale GitHub issues involves identifying what is open, grouping related tickets by root cause, and verifying close candidates against the current codebase. This avoids false closes and only surfaces well-supported results for backlog cleanup.

How do I classify CodeRabbit-generated issues separately from manual bug reports?▼

You can classify CodeRabbit-generated issues separately from manual bug reports by inventorying all open tickets and sorting them into distinct categories. This separation clarifies whether an issue stems from automated analysis or manual observation for better triage prioritization.

Can I verify if a GitHub issue is ready to close by checking the current codebase?▼

GitHub issue triage is suitable for any repository needing backlog cleanup, including those with mixed CodeRabbit-generated and manual reports across bug, feature, epic, and refactoring categories. It works by inventorying issues and verifying close candidates against the codebase.

How do I group related GitHub issues by root cause for batch fixes?▼

You group related GitHub issues by clustering tickets with shared code areas or underlying problems. This root-cause grouping makes batch fixes easier to plan and execute by surfacing related issues that can be resolved together.

Related Skills

Explore More Software Engineering Skills→
BAS-MoreBAS-More

triage

Classify and label GitHub issues using the GitHub CLI.

Official
Intermediate
BrunoAMSilvaBrunoAMSilva

critical-partner

Reviews pull requests and architectural proposals for defects and risks.

Community
Advanced
dakshrawat298-gifdakshrawat298-gif

security-fix-review

Review security patches for root-cause coverage and bypass risks.

Community
Intermediate
bryan-thompsoncodesbryan-thompsoncodes

workday-sprint

Categorize GitHub Project V2 sprint items by Status for Bryan.

Community
Intermediate