undefined-ui/second-brain-os / skills/second-brain-merge
second-brain-merge
VerifiedMerge 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.8 KB |
SKILL.md
View on GitHub---
name: second-brain-merge
description: >-
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.
---
# 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.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |