Oh My Issues

If your issue tracker has accumulated dozens of reports that smell like duplicates but nobody has the nerve to close them, this is the clustering pass you've been putting off. It reads every open issue plus comment threads, groups symptoms by shared architectural root cause, opens one plan-master issue per cluster with a design doc in `plans/`, and closes children with a standardized redirect. The end state is open issues equals open plans, one to one. After the initial reduction it handles triage for new bugs and bundles PRs that close entire clusters atomically with a test matrix that prevents reoccurrence. Works best on backlogs of twenty plus issues where you suspect five real problems hiding under thirty surface complaints. Ships the discipline to keep it that way.

skills.sh installs: 4.3K
GitHub stars: 115.5K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add thedotmack/claude-mem --skill oh-my-issues --agent claude-code

Installs into .claude/skills of the current project.

Files

oh-my-issues

Turn an issue backlog into a roadmap. Issues are symptom data, not units of work — the unit of work is the architectural defect that produces them. The end state is open issues == open plans, 1:1.

Core principle

Stop closing issues one at a time. Group symptoms that share a single architectural fix into a cluster, give the cluster one canonical home (a plan-master issue whose body is the design), close every child with a standardized redirect, and ship one PR per cluster that closes all children atomically. New incoming bugs get appended to the matching master as a "Round N" comment, not opened as new tracked issues.

This compounds three ways: architectural fixes retire whole symptom families, the plan's test matrix institutionalizes prevention in CI, and standardized triage makes residual inflow cheap.