wiki-update

Obsidian wiki syncing works by reading your project directory and local vault manifest, then writing new pages with architecture decisions and learnings. It compares against the last synced state to ensure only delta updates are pushed.

No, wiki syncing is delta-aware and reference-driven. It reads the vault index and manifest to compare against the last synced state, avoiding duplicates and preserving your existing structure while only reflecting changes since the last sync.

Yes, you can push architecture decisions from any project folder. The skill operates across any project directory to extract patterns and learnings, writing them as new pages under the projects/<project-name>/ path in your vault.

The best way to keep Obsidian vault notes updated is using a delta-aware sync process. This skill reads the wiki manifest to identify changes since your last sync and distills new project knowledge into concise wiki pages for future reference.

No, you do not need to manually organize synced project files. The skill automatically writes new pages under a structured projects/<project-name>/ directory, preserving your vault structure by reading the existing configuration and vault index.