obsidian-sync

Name: obsidian-sync
Availability: InStock
Author: brandondaymdr

Synchronize CLAUDE.md project documentation into Obsidian vault notes.

1|Updated Feb 19, 2026

Search Tags:#documentation #productivity #knowledge management #knowledge base #obsidian #sync

Ready to run

npx skills add https://github.com/Brandondaymdr/Claude-Skills --skill obsidian-sync-brandondaymdr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: obsidian-sync
Source: https://github.com/Brandondaymdr/Claude-Skills/tree/main/obsidian-sync
Command: npx skills add https://github.com/Brandondaymdr/Claude-Skills --skill obsidian-sync-brandondaymdr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the problem of fragmented project knowledge by ensuring that architecture decisions, status updates, and technical gotchas captured during coding sessions are automatically persisted into your personal Obsidian knowledge base.

Core Features & Use Cases

Automated Knowledge Capture: Diffs your CLAUDE.md against existing Obsidian notes to identify and merge new project insights.
Context Preservation: Maintains a structured project history including architecture, status, and references without manual copy-pasting.
Use Case: After finishing a complex feature implementation, trigger this skill to automatically update your project note with the new technical gotchas and status changes recorded in your session.

Quick Start

Trigger the obsidian-sync skill by telling the assistant to update my vault with the latest session changes.

Frequently Asked Questions about obsidian-sync

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

FAQPage Schema

How do I sync coding session knowledge to Obsidian vaults?▼

Sync coding session knowledge by diffing your project's CLAUDE.md against existing Obsidian markdown notes. The skill automatically identifies and appends architecture decisions, status updates, and technical gotchas to your vault using non-destructive content merging.

How does automated knowledge capture for project documentation work?▼

Automated knowledge capture works by comparing your project's CLAUDE.md against existing Obsidian markdown notes to identify new session insights. It automatically appends architecture decisions, status updates, and technical gotchas to your knowledge base without manual copy-pasting.

Do I need filesystem access to sync project documentation to a local Obsidian vault?▼

Yes, syncing project documentation requires filesystem access to both your project directory and the local Obsidian vault path. This access enables the tool to read CLAUDE.md session insights and perform non-destructive content merging into existing markdown notes.

Can I update Obsidian notes with session changes without overwriting existing content?▼

Yes, you can update Obsidian notes without overwriting existing content. The synchronization performs non-destructive content merging, ensuring new architecture decisions and technical gotchas are appended to your markdown files rather than replacing existing project history.

What's the best way to preserve context across coding sessions in a knowledge base?▼

The best way to preserve context is to synchronize CLAUDE.md into Obsidian vault notes. This maintains a structured project history including architecture decisions, status updates, and references automatically after finishing complex feature implementations.