sync-orientation-docs

Scan orientation docs and propose surgical edits after repository changes.

12|2|Updated Jun 8, 2026

Search Tags:#documentation #claude code #subagent #sync #repo maintenance #orientation docs

Ready to run

npx skills add https://github.com/Loringtonian/second-brain-template --skill sync-orientation-docs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sync-orientation-docs
Source: https://github.com/Loringtonian/second-brain-template/tree/main/.claude/skills/sync-orientation-docs
Command: npx skills add https://github.com/Loringtonian/second-brain-template --skill sync-orientation-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill keeps the repository's orientation documents aligned with real changes so the navigation layer stays trustworthy after file moves, status updates, skill edits, and structural changes.

Core Features & Use Cases

Doc Coherence Checks: Reads the full orientation doc set to find stale references and downstream inconsistencies.
Cascade-Aware Proposals: Traces changed names, folders, and skills across related docs so hidden references are not missed.
Safe Change Workflow: Produces surgical edit proposals instead of applying changes directly, preserving review control.
Use Case: After renaming a project folder or updating a skill, the Skill can identify every orientation doc that should reflect the change and draft exact replacements.

Quick Start

Ask the agent to sync the orientation docs after a file, folder, status, or skill change and review the proposed edits before applying them.

Frequently Asked Questions about sync-orientation-docs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I keep orientation docs in sync after moving files or renaming folders?▼

To keep orientation docs in sync after structural changes, perform a full-doc scan and count verification to detect stale references and downstream inconsistencies. You then review surgical edit proposals before applying them, ensuring the navigation layer stays trustworthy without losing review control.

How do you trace cascade effects when updating skill references in documentation?▼

Tracing cascade effects involves scanning the full orientation doc set to detect hidden references impacted by changed names, folders, or skills. Cascade-aware proposals trace these structural changes across related docs to ensure no downstream inconsistencies are missed before edits are applied.

Can I automatically update documentation references without losing review control?▼

Yes, you can update documentation references without losing review control by using a safe change workflow. The process requires a full-doc scan and proposed edit reporting before any changes are applied, producing surgical edits instead of applying changes directly.

When do I need to run a documentation coherence check for repo maintenance?▼

You need to run a documentation coherence check for repo maintenance after file operations, status transitions, structural changes, or skill edits. These actions can ripple through navigation docs, requiring a full-doc scan and count verification to identify stale references.

What is the best way to find stale references in a second-brain repository?▼

The best way to find stale references in a second-brain repository is performing a doc coherence check. This reads the full orientation doc set to locate downstream inconsistencies and hidden references, generating cascade-aware proposals for exact replacements before applying changes.

Are there limitations to automatically synchronizing orientation docs?▼

A limitation of synchronizing orientation docs is that the process cannot apply changes directly. It requires count verification, cascade detection, and proposed edit reporting first, meaning you must manually review and approve surgical edits before the navigation docs are updated.