oh-my-issues

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

1|Updated Apr 27, 2026
One-click install
npx skills add https://github.com/dwaynimay/IoTProject --skill oh-my-issues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oh-my-issues
Source: https://github.com/dwaynimay/IoTProject/tree/main/.agents/skills/oh-my-issues
Command: npx skills add https://github.com/dwaynimay/IoTProject --skill oh-my-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of an issue backlog becoming unmanageable by clustering related reports into architectural root-cause plans, keeping the work unit aligned to lasting fixes rather than symptoms.

Core Features & Use Cases

  • Cluster symptom issues into architectural defect plans: Groups many open issues under a smaller set of master plan issues with a consistent title and structure.
  • Standardize triage with redirect comments: Closes child issues with a uniform redirect so contributors always know where progress is tracked.
  • Bundle fixes into atomic PRs per cluster: Produces one PR per plan slice that closes all children together and uses a required test matrix to prevent regression.
  • Ongoing mode for new incoming bugs: Routes new issues to the correct existing plan master via “Round N” consolidation comments instead of letting the backlog grow again.

Quick Start

Use the oh-my-issues skill to triage a growing GitHub backlog by clustering open issues into plan-master issues, redirecting children with the standardized comment, and preparing plan-scoped PRs with a CI test matrix.

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 a GitHub issue backlog by root cause?

Standardize issue triage by closing child issues with a uniform redirect comment that funnels contributors to the master plan issue. This ensures progress is always tracked at the architectural root-cause level rather than across scattered symptom reports.

How do I bundle plan slices into atomic PRs that close related issues together?

Bundle plan slices into atomic PRs by creating one PR per cluster that closes all child issues simultaneously, paired with a required CI test-matrix update. This prevents regression by ensuring all related fixes ship and test together.

Can I route new incoming bugs to existing plan masters during ongoing triage?

Route new incoming bugs to existing plan masters using ongoing mode, which applies “Round N” consolidation comments to redirect new issues. This prevents the backlog from growing again by continuously mapping new reports to established architectural plans.

What is needed to generate plan design docs for consolidated GitHub issues?

Generating plan design docs for consolidated GitHub issues requires full ingestion of issue bodies and comment threads to cluster reports by root cause. The output includes standardized master plan issues with consistent titles, structures, and CI test-matrix updates.

Does issue triage work without ingesting full comment threads?

Issue triage clustering requires full issue-body and comment-thread ingestion to accurately identify root causes and map open issues to open plans. Without complete comment data, the root cause clustering and 1:1 plan mapping cannot be reliably generated.