oh-my-issues

仓库创建 2025年9月1日最近提交 4 天前SkillHot 收录 21 天前

▸ 精选理由

把零散报告转成可执行的架构性修复计划，提升维护效率。

▸ 风险提示

需要对 GitHub 仓库的读写权限，会发布评论或关联 PR

这个 Skill 做什么

把大量问题按根因聚类并生成计划主 issue 与标准回复。

把一堆看似不同的 GitHub issue 按根因聚类，给每个根因建一个 plan‑master（主计划）issue，再用标准回复把子 issue 引导到那里，同时把修复性 PR 打包成能原子关闭整簇的变更。适合问题多、重复报 bug、或想把 issue 库变成可执行路线图时使用。它的特点是把症状归结为可执行的修复计划，避免零碎逐个处理浪费精力。

▸ 展开 SKILL.md 英文原文

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. Use when an issue tracker has accumulated dozens of reports that share underlying defects, when asked to triage / consolidate / cluster / dedupe issues, when asked to build a plan series or roadmap from open issues, or when routing a new incoming bug into an existing plan.

开发编程Issue 聚类路标化GitHub通用

8.9w

Stars

7.7k

Forks

仓库内 Skill

+2.6k

7 日增星

安装 / 使用

给你的 Agent 一句话（通用）

帮我安装这个 skill：https://raw.githubusercontent.com/thedotmack/claude-mem/main/plugin/skills/oh-my-issues/SKILL.md

或 curl 直取 SKILL.md

curl -fsSL "https://raw.githubusercontent.com/thedotmack/claude-mem/main/plugin/skills/oh-my-issues/SKILL.md"

SKILL.MD 节选查看完整文件 ↗

# 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 + a `plans/0X-*.md` design doc), 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 fixe

via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有