← ClaudeAtlas

atlas-mergelisted

Merge the wikis of a hub's members into the hub's own: find the pages two members wrote about one thing and upgrade them into the hub, and build bridge pages that join neighbouring pages across members, as one merge the user approves. Use for merge the members, consolidate the wikis, merge the knowledge bases, what overlaps across projects, find duplicates across projects, bridge the vaults, upgrade pages to the parent, adopt a new member's wiki. Duplicates inside one wiki are wiki-review's.
nathanaday/atlas-obsidian · ★ 0 · Code & Development · score 72
Install: claude install-skill nathanaday/atlas-obsidian
# Merge the members' wikis A hub mirrors its members' wikis under `wiki/projects/<name>/`. Each member wrote its pages alone, so two of them hold pages about one thing without knowing it, and the overlap is visible only here. This skill finds it cheaply, reads only the pages that matter, and proposes one merge the user approves before anything is written. Tools: `status`, `project`, `overlap`, `route`, `plan`, `apply`. Reads [operations.md](../wiki/references/operations.md) and [provenance.md](../wiki/references/provenance.md). The merge has two moves: - **Upgrade.** Two or more origins hold the same thing. One page in this wiki takes their content, written from the member versions and citing the members' source pages through the mirror. Each member page becomes a pointer: the same file, its frontmatter gaining `moved_to` and `moved_to_project`, its body one line saying where the page went. The member's own links to it still resolve, and the next sync sends every link to the hub's page and mirrors the pointer no more. - **Bridge.** Two origins hold neighbouring things: Linux in one, macOS in another, or two pages that link the same name nobody wrote. One new page in this wiki names what they share and links both, with full vault paths into the mirrors. Nothing in a member changes. Everything acts on this session's project; a member changes only through a `plan` that names it with `project`, as its own operation, with the user's yes. ## Find the overlap