Second Brain Rename
Rename a page safely: update the file, fix every inbound wikilink, add the old name as...
Install
npx skills add undefined-ui/second-brain-os --skill second-brain-rename -g -a claude-code -y- Repository
- undefined-ui/second-brain-os1.2k
- Category
- Engineering
- Updated
- 22d ago
- License
- MIT
- Context cost
- Lightabout 306 tokens
- Runs scripts
- No, instructions only
What it does
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.
Rename a page
An agent renaming a file directly is the single most common source of broken links in an agent-maintained vault. Obsidian fixes links when you rename inside the app; writing the file directly does not.
Core rule
A rename is four operations, not one. All four, or none.
Workflow
- Check the new name against existing pages and aliases. A rename that collides with an existing alias creates ambiguity the graph cannot resolve.
- Rename the file and update the
titlein frontmatter. - Add the old title to
aliases. This keeps external references, the user's memory, and any link you miss working. - Update every inbound link. Search the whole vault, including
index.md. - Log it: old name, new name, links updated.
- Verify with a link check.
Output format
Renamed: [[old]] -> [[new]]
Inbound links updated: <n> across <n> pages
Alias added: <old>
Remaining references: <none | list>
Calibration
Do not rename to fix a style preference on a page with many inbound links. The cost is real and the benefit is cosmetic.
If the correct name is genuinely ambiguous, ask rather than picking. A second rename is more disruptive than the first.
