obsidian-enrich

To sync technical documentation to an Obsidian vault, you can extract architecture details and coding conventions directly from project-level CLAUDE.md files. This maps project directories to specific vault notes, maintaining a synchronized, high-context knowledge base for development sessions.

Updating Obsidian notes with new project progress without overwriting manual annotations is possible through intelligent merging. The system extracts high-value technical details like system architecture and database schemas, integrating them while preserving your existing manual notes and observations.

Extracting database schemas and architecture details from CLAUDE.md files requires context extraction. This process parses the project files to automatically identify and structure high-value technical information, including known issues, build commands, and current roadmap status directly from the source.

The best way to maintain a synchronized knowledge base for development sessions is mapping project repositories to specific vault notes. This requires direct filesystem access to both the target project repositories and the vault to perform discovery, extraction, and structured writing.

Filesystem access to the target project repositories and the Obsidian vault is required. This direct filesystem access enables the system to perform discovery, extraction, and structured writing operations necessary to map project directories and maintain a high-context knowledge base.

You should avoid using automated context extraction when a project repository lacks structured CLAUDE.md files or supplementary architecture documents. The system relies on parsing these specific files to extract technical details, so fragmented or missing source documentation will limit its effectiveness.