Claude-Mem Issue Backlog Clustering

thedotmack/claude-mem

Cluster GitHub issues by shared root cause, create canonical plan issues, and prepare coherent fix bundles.

Contenu mis à jour:

Dans la collectionClaude-Mem ↗
Voir sur GitHub
npx claude-mem install
116 859Étoiles10 141ForksDernier push du dépôt

À propos de ce Skill

Cluster GitHub issues by shared root cause, create canonical plan issues, and prepare coherent fix bundles.

Pourquoi ce choix

A reusable workflow from the Claude-Mem project. It is listed separately to explain this task; shared runtime and helper dependencies remain part of the upstream installation. The inherited gallery demonstrates the memory system, not this task’s specific output.

À quoi il sert

  • Turn many overlapping reports into a smaller set of actionable architectural fixes.

How the workflow runs

  1. Step 1

    Read the actual issue inventory and comment threads, accounting for pagination.

  2. Step 2

    Group symptoms by shared architectural defect and draft a canonical plan for each cluster.

  3. Step 3

    With authorization, redirect child reports and bundle fixes with clear closure criteria.

Original oh-my-issues instructions

Expected result

Root-cause clusters, canonical plan issues, and an implementation roadmap.

Original oh-my-issues instructions

Try a concrete request

  1. Example request

    After installing the required integration, ask your agent:

    Review this repository’s open issues and propose root-cause clusters before changing any issue.

Avant de l’utiliser

  • GitHub CLI authentication and issue access. Creating comments, closing issues, and merging changes need the user’s authorization.
  • Use the original upstream files and follow the documented host integration. Model or third-party service usage can carry separate costs.

Agents compatibles

Claude CodeCodex CLI

Sources et références

Les sources originales sont liées ci-dessous. Les pistes pratiques sont des suggestions de la rédaction de SkillHey.