Skip to content

undefined-ui/second-brain-os / skills/second-brain-rename

second-brain-rename

Verified

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

  1. Check the new name against existing pages and aliases. A rename that collides with an existing alias creates ambiguity the graph cannot resolve.
  2. Rename the file and update the title in frontmatter.
  3. Add the old title to aliases. This keeps external references, the user's memory, and any link you miss working.
  4. Update every inbound link. Search the whole vault, including index.md.
  5. Log it: old name, new name, links updated.
  6. 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.

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: 466kUpdated Claude CodeCodexVerifiedInstall
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: 466kUpdated Claude CodeCodexVerifiedInstall
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: 319kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 319kUpdated Claude CodeCodexVerifiedInstall