skills.rest
Intelligent-Resourcing-Team-Environment
Intelligent-Resourcing-Team-EnvironmentOFFICIAL
Explore all skills by this author →
WebsiteGitHub

oh-my-issues

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

Updated Jun 19, 2026
Search Tags:#planning#architecture#github#backlog#issues#triage#root-cause
One-click install
npx skills add https://github.com/Intelligent-Resourcing-Team-Environment/claude-memory --skill oh-my-issues-intelligent-resourcing-team-environment
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: oh-my-issues
Source: https://github.com/Intelligent-Resourcing-Team-Environment/claude-memory/tree/main/plugin/skills/oh-my-issues
Command: npx skills add https://github.com/Intelligent-Resourcing-Team-Environment/claude-memory --skill oh-my-issues-intelligent-resourcing-team-environment

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cluster a GitHub issue backlog by root cause into a small set of plan-master issues, redirect children with a standardized comment, and bundle architectural-fix PRs that close clusters atomically.

Core Features & Use Cases

  • Triage and cluster open issues by architectural defect, producing a canonical plan-master per cluster.
  • Create plan masters with a design doc and link to their child issues.
  • Redirect closed issues with a standardized comment and bundle changes into PRs that close all children atomically.
  • Round N triage comments on masters for new incoming bugs to attach them to existing plans.

Quick Start

Create a plan master for a root-cause cluster by consolidating related issues and close all children with the standard redirect comment.

Frequently Asked Questions about oh-my-issues

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

FAQPage Schema
How do I triage a large GitHub issue backlog by root cause?▼

Triage a GitHub issue backlog by clustering symptom-level issues into plan-master issues based on their architectural root cause, then redirecting children with standardized comments and closing them atomically via bundled PRs.

What is the best way to consolidate duplicate GitHub issues into a single plan?▼

Consolidate duplicate GitHub issues by creating a canonical plan-master issue with a design doc, linking related child issues to it, and applying a standardized redirect comment to close the children.

Can I bundle architectural fix PRs to close multiple GitHub issues atomically?▼

You can bundle architectural-fix PRs that close issue clusters atomically. This enforces structured master-child relationships and integrates cross-issue PRs to enable end-to-end backlog consolidation.

How do I attach new incoming bugs to existing GitHub plan master issues?▼

Apply Round N triage comments on existing plan masters to attach new incoming bugs to established plans, ensuring continuous backlog consolidation without creating redundant root-cause clusters.

When should I use plan-master issues over individual GitHub bug reports?▼

Use plan-master issues when managing repositories with large open backlogs of symptom-level issues, allowing teams to map work into structured master-child relationships and corresponding plan documents.

Does triaging GitHub issues by architecture require writing design docs?▼

Creating plan masters for root-cause clusters involves producing a design doc and linking it to child issues, ensuring the architectural fix has a documented plan before closing children.

Related Skills

Explore More Software Engineering Skills→
ybbms777ybbms777
1

issue-intelligence-analyst

Analyze GitHub issue trackers to extract recurring pain patterns and severity trends.

Community
Advanced
dwaynimaydwaynimay

oh-my-issues

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

Community
Advanced
spboyerspboyer

repo-issue-triage

Cross-reference GitHub issues against PRs and main branch for triage reports.

Community
Advanced
chicago-joechicago-joe

oh-my-issues

Cluster GitHub issue backlogs by root cause into plan-master issues.

Community
Advanced