codebase-maintenance

You can sync Obsidian vault documentation with code changes by analyzing your current branch, mapping the code modifications to existing vault notes, and updating drifted references to keep both layers aligned. This prevents documentation from becoming stale during development.

Skill drift detection identifies outdated paths, configurations, and references across project skills. It heals these references by auditing the drifted configurations and updating them to match the current project state, reducing wasted effort and misalignment.

You can clean up code and check vault documentation health simultaneously by specifying a full maintenance scope. This coordinates code cleanup with vault health checks to surface stale notes and missing docs in a single workflow.

No external dependencies are required for standard runs. The maintenance workflow operates across code cleanup, vault documentation, and skill synchronization natively without needing extra packages or tools installed.

The best way to safeguard against destructive actions is to use planning-mode. This generates an actionable plan first and performs changes with built-in safeguards, ensuring you can review modifications before they are applied.

Yes, you can target only the vault by specifying vault as your scope. This limits the workflow to documentation health checks and note synchronization without running code cleanup or skill audits.