second-brain-merge

Solid

Merge two pages that describe the same thing, preserving every distinct claim, redirecting inbound links, and recording the merge. Use this skill when the user approves a duplicate merge, says "these are the same page", "merge X into Y", or asks to clean up near-duplicates that a lint run proposed. Do NOT use to merge pages on your own judgement, to delete a page outright, or to split one page into several.

AI & Automation 46 stars 7 forks Updated today MIT

Install

View on GitHub

Quality Score: 81/100

Stars 20%
56
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
70
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Merge duplicate pages A merge is irreversible in the way that matters: afterwards you cannot tell which claim came from which page. Two ideas that look identical from their summaries are often a general case and a specific one. ## Core rule Never merge unprompted. Propose, wait for approval, then follow the procedure exactly. ## Workflow 1. **Pick the survivor** by canonical name, not by which page is longer. 2. **Merge content.** Every distinct claim survives with its source. Overlapping claims collapse; differing ones both stay, following the contradiction rules. 3. **Merge aliases,** including the dead page's title as an alias on the survivor. This is what keeps old links and the user's memory working. 4. **Redirect inbound links** to the survivor. Check every backlink. 5. **Delete the old page,** or leave a stub only if it was linked from outside the vault. 6. **Record in `log.md`:** both names, the date, and why. ## Output format ``` Merged: [[old]] -> [[survivor]] Claims kept from old page: <n> Aliases added: <list> Inbound links redirected: <n> Conflicts recorded: <none | description> ``` ## Calibration If the two pages disagree about anything factual, that is a signal they may not be duplicates. Surface the disagreement and ask before proceeding. Never merge a page marked `maintained_by: human` into another without explicit confirmation naming that page.

Details

Author
undefined-ui
Repository
undefined-ui/second-brain-os
Created
3 days ago
Last Updated
today
Language
HTML
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

cx-content-consolidation

Use to merge overlapping help articles without breaking search, bookmarks, or AI grounding — choosing a canonical page, setting redirects, and measuring post-merge impact. Trigger for "we have duplicate KB articles", consolidate help centre content, merge knowledge base articles, KB deduplication, article redirects, canonical help article, or overlapping docs confusing customers and search.

1 Updated 1 months ago
rulebase-co
AI & Automation Solid

second-brain-rename

Rename a page safely: update the file, fix every inbound wikilink, add the old name as an alias, and log it. Use this skill whenever a page needs a different canonical title, the user says "rename X to Y", asks to fix an inconsistent title, or after a lint run flags naming problems. Do NOT use for merging two pages, for moving a page between folders without a name change, or for renaming files outside the wiki.

46 Updated today
undefined-ui
AI & Automation Solid

human-merge

Takes several separate reports — from several agents, several sources, or several documents — and returns one surface a person can decide from. Each report may be individually fine; the pile is what defeats the reader, and the relations between reports are invisible to every author who wrote one. Collapses reports that share an upstream source into the single source they are, names what is now superseded and whether a live decision rests on the dead figure, classifies conflicts instead of averaging them away, and pools coverage so a gap no single report had becomes visible. Works on any subject: research, legal, finance, operations, conservation, code. Trigger phrases: "/human-merge", "merge these reports", "combine what the agents found", "what do all of these add up to", "the sub-agents all came back", "did anything here contradict anything else". Not /human-output (the writing contract, which this skill links to rather than restates) or /human-rewrite (repairs one existing text and explicitly refuses sever

14 Updated yesterday
allemaar