skills.rest
trehansalil
trehansalilCOMMUNITY
Explore all skills by this author →
Website𝕏@trehansalilGitHub

oh-my-issues

Cluster GitHub issues by root cause and redirect them to plan-master issues.

Updated Jun 14, 2026
Search Tags:#github#issue management#issue clustering#pr bundling#issue redirection
One-click install
npx skills add https://github.com/trehansalil/claude-mem-deploy --skill oh-my-issues-trehansalil
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: oh-my-issues
Source: https://github.com/trehansalil/claude-mem-deploy/tree/main/image/plugin/skills/oh-my-issues
Command: npx skills add https://github.com/trehansalil/claude-mem-deploy --skill oh-my-issues-trehansalil

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps manage a large number of GitHub issues by clustering them into plan-master issues, redirecting children with a standardized comment, and bundling architectural-fix PRs that close clusters atomically.

Core Features & Use Cases

  • Issue Clustering: Automatically group issues with the same root cause into clusters.
  • Standardized Redirect: Close child issues with a standardized comment redirecting to the master issue.
  • PR Bundling: Create a single PR to close all issues in a cluster atomically.
  • Use Case: When you have a large number of related issues that need to be addressed as part of a larger plan.

Quick Start

Use the oh-my-issues skill to cluster and redirect all open issues in the 'infra' namespace.

Frequently Asked Questions about oh-my-issues

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

FAQPage Schema
How do I cluster GitHub issues that share the same root cause?▼

You can group GitHub issues into a plan-master issue based on root cause, automatically redirecting child issues with a standardized comment and bundling architectural-fix PRs to close them atomically.

What is the best way to bundle PRs to close multiple related GitHub issues atomically?▼

Bundling PRs to close GitHub issues atomically involves creating a single architectural-fix PR mapped to a cluster's plan-master issue, ensuring all related child issues are resolved simultaneously when the PR merges.

Do I need the GitHub API and gh CLI to automate issue redirection?▼

Yes, automating issue redirection requires GitHub API access and the gh CLI dependency to programmatically manage issue states, post standardized redirect comments, and handle plan-master issue creation.

How do I manage a large number of GitHub issues as part of a larger architectural plan?▼

Managing large numbers of GitHub issues involves clustering them into plan-master issues, providing a standardized redirect comment for closed child issues, and bundling PRs to address the architectural plan atomically.

When should I use issue clustering instead of managing GitHub issues individually?▼

Use issue clustering when you have a large number of related GitHub issues that need to be addressed as part of a larger plan, allowing you to bundle architectural-fix PRs and close clusters atomically rather than individually.

Related Skills

Explore More Software Engineering Skills→
georgekhananaevgeorgekhananaev
27

github-cli

Wrap GitHub CLI commands with risk classification and confirmation prompts.

Community
Intermediate
Intelligent-Resourcing-Team-EnvironmentIntelligent-Resourcing-Team-Environment

oh-my-issues

Cluster GitHub issues by root cause into plan-master issues with redirect comments.

Official
Advanced
dwaynimaydwaynimay

oh-my-issues

Cluster GitHub issue backlogs into architectural plan-master issues with redirect comments.

Community
Advanced
j5ik2oj5ik2o
7

gh-issue-organizer

Organize and triage GitHub issues by cause and closure readiness.

Community
Intermediate