knowledge-wiki-template: Skill for Claude Code

Knowledge Wiki Cluster

Detect clusters of concepts that share an implied parent slug, then decide for each child whether to fold (merge content into parent and delete the child) or link (keep the child as a standalone concept linked to the parent). The goal is to reduce total concept count by absorbing thin, redundant, or retired sub-concepts into a parent article.

Two cluster types are handled:

• New-parent (parentExists: false): the implied parent concept does not exist yet — create it, then fold/link/merge children.
• Existing-parent (parentExists: true): the implied parent already exists and these children have not yet been dismissed — fold/link/merge each one.

For new-parent clusters, each concept is grouped under its non-existing prefix ancestors up to (but not including) its nearest existing ancestor — so apple-watch-ultra forms an [apple-watch] cluster when apple-watch.md is absent, even if apple.md exists. For existing-parent clusters, the concept is grouped directly at its nearest existing ancestor. Presents one cluster at a time with a batch recommendation — you confirm, override, or dismiss.

Within a cluster, children may also be merged into each other (sibling merging) before any folding into the parent. A child judged not worth folding into the parent — an Anchor — can absorb another child's content if that child — a Fold-candidate — is a strict subset of the Anchor's content. The absorbed Fold-candidate is merged into the Anchor and deleted; the Anchor is recommended to stay standalone and is not expected to be folded into the parent.

Steps

1. Establish the working directory

The knowledge base root is the Git repository root. Run git rev-parse --show-toplevel and store the result as KNOWLEDGE_PATH.

2. Find clusters

Run:

node {KNOWLEDGE_PATH}/scripts/wiki/candidates.mjs find-implied-parent-concepts

This outputs { "clusters": [...] } sorted deepest first (most hyphens in impliedParent), with ties broken by cluster size descending. Both new-parent and existing-parent clusters are interleaved in this single ordering. Each entry has:

• impliedParent — the parent slug
• children — array of { path, dismissed } objects, where path is the concept file path (e.g. Wiki/Concepts/audi-etron.md) and dismissed is true if this child was previously dismissed from this cluster pair, false otherwise
• parentExists — false if the parent concept needs to be created; true if it already exists