oh-my-issues (Issue Backlog Clustering)
Turns a sprawling GitHub issue backlog into a handful of root-cause "plan-master" issues plus a shippable roadmap.
Dev & CodingIntermediate★ 90,139⑂ 7,846AI score 8/10Last updated: Aug 9, 2026
What it does
Reframes an issue tracker as a roadmap of architectural defects instead of a pile of symptoms.
- Reads every open issue's full body and comment thread, then clusters by the question "would one architectural change retire all of these?"
- Opens one master per cluster titled
[plan-XX] <Architectural Defect> — <one-line scope>, mirrored as aplans/0X-*.mddesign doc - Closes each child with a standardized redirect comment and
not planned - Routes new incoming bugs into the matching master as a "Round N" comment (Mode 2)
- Ships one PR per cluster listing
Closes #Nso all children close atomically (Mode 3)
It also documents real gh CLI gotchas: --json comments returns only counts, --limit truncates silently, and the REST issue count includes PRs.
Who it's for
- Open-source maintainers buried under 20+ (or ~100) open issues that look like duplicates
- Team leads who want work defined by root cause rather than surface labels like "Windows bugs"
- Teams introducing a 1:1 discipline between the tracker and a
plans/directory - Anyone who wants regression test matrices institutionalized in CI
Examples
- Initial reduction (Mode 1): "Read all 90 open issues and cluster them by root cause" → 4–8 plan masters plus
plans/0X-*.mddocs; everything else closed with the redirect comment. - Triage (Mode 2): "Which plan does the new issue #217 belong to?" → a Round 3 comment on the master with the symptom, a 1–3 line fix sketch, and the new test-matrix cell, then the child is closed.
- Bundle (Mode 3): "Draft the PR for the plan-02 slice" → PR body listing
Closes #Nfor every covered child, with the plan's test matrix added to CI.
· · · Install guide · · ·
Install in the Claude app (no terminal)
- Download the ZIP with the button below.
- In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
- Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.
Install in Claude Code
Let Claude do it — paste this into Claude Code
Install the skill I found on Claude Skill Mart. Copy the plugin/skills/oh-my-issues folder from the GitHub repo thedotmack/claude-mem into my ~/.claude/skills/oh-my-issues/. When it's done, tell me in one line what this skill can do.
Install with a command instead
git clone https://github.com/thedotmack/claude-mem.git /tmp/claude-mem && mkdir -p ~/.claude/skills && cp -r /tmp/claude-mem/plugin/skills/oh-my-issues ~/.claude/skills/ && rm -rf /tmp/claude-mem⚠ This is a third-party skill. Check the source repository before installing.
- Confirm GitHub CLI is installed:
gh --version(install from https://cli.github.com if missing). - Check auth and scopes:
gh auth status— the account needs permission to create and close issues. - Clone the repository:
git clone https://github.com/thedotmack/claude-mem.git /tmp/claude-mem - Copy the skill into your personal skills folder:
mkdir -p ~/.claude/skills && cp -r /tmp/claude-mem/plugin/skills/oh-my-issues ~/.claude/skills/ - Clean up:
rm -rf /tmp/claude-mem - Start Claude Code inside the repo you want to triage and ask it to "cluster the issue backlog by root cause" — the skill triggers automatically.
- Important: Ask for a proposed cluster list first and review it before allowing any issue closures; trying it on a fork or test repo first is strongly recommended.
View source on GitHub ↗License: Apache-2.0