Cluster GitHub issue backlogs by root cause into plan-master issues.
npx skills add https://github.com/chicago-joe/manymems --skill oh-my-issues-chicago-joe
Please help me install this Agent Skill. Skill: oh-my-issues Source: https://github.com/chicago-joe/manymems/tree/main/plugin/skills/oh-my-issues Command: npx skills add https://github.com/chicago-joe/manymems --skill oh-my-issues-chicago-joe
Cluster GitHub issue backlogs by root cause into a small set of plan-master issues, enabling efficient triage, consolidation of duplicates, and a roadmap.
Triage your open issues by root cause, create plan-master issues, and redirect duplicates to their master plan.
High-intent search queries and answers about installing and using this skill.
To cluster a GitHub issue backlog by root cause, you triage reported symptoms and consolidate them into a small set of plan-master issues. This exposes architectural defects and enables efficient roadmap planning by routing duplicates to canonical plans.
A plan-master workflow for issue triage is a process where you open master plan issues and corresponding design docs under plans/. You redirect each symptom to the master plan with a standardized comment to consolidate duplicates and manage architectural fixes.
You consolidate duplicate GitHub issues by clustering them by root cause into plan-master issues. This enables roadmap planning by atomically closing all related children via PRs once the underlying architectural fix is bundled and merged.
Yes, you can route new incoming bugs to existing plan-master issues as Round N updates. This applies to repositories with many reported symptoms, allowing continuous triage by redirecting new duplicates to their canonical plans.
Automated issue triage using this plan-master approach requires creating design docs in a plans/ directory. These docs accompany the plan-master issues to document the architectural fixes needed for the clustered root causes.
The best way to close clustered GitHub issues atomically is to bundle the architectural fixes into Pull Requests. When the PR merges, it closes all related child issues routed to the plan-master simultaneously.
ybbms777Analyze GitHub issue trackers to extract recurring pain patterns and severity trends.
Intelligent-Resourcing-Team-EnvironmentCluster GitHub issues by root cause into plan-master issues with redirect comments.
PlagueHOMerge ready Dependabot PRs in parallel with status reports.
trehansalilCluster GitHub issues by root cause and redirect them to plan-master issues.
