Sync to Obsidian — Auto-Detect Project Sync

Automatically sync your Claude Code session plans and implementation reports to your Obsidian vault.

Every sync produces two files: a detailed Markdown note + an Obsidian Canvas visual map.

The project name is auto-detected — no per-project configuration needed.

Configuration

Only one path to set — your Obsidian vault root:

CODEBLOCK0

Update this to your actual Obsidian vault path before first use.

Auto Project Detection

The skill automatically detects the current project name (in priority order):

1. 1. Git repo name: INLINECODE0
2. Current directory name: basename $PWD (fallback if not in a git repo)

Sync targets are derived from the project name:

• - Markdown: INLINECODE2
• Canvas: INLINECODE3

Directories are auto-created if they don't exist (mkdir -p).

Usage

CODEBLOCK1

• - $ARGUMENTS[0]: Type — plan or report (required)
• INLINECODE8: Custom title (optional — auto-inferred from content if omitted)

Execution Flow

Step 0: Detect Project

1. 1. Run basename $(git rev-parse --show-toplevel 2>/dev/null) 2>/dev/null || basename $PWD to get project name
2. Set INLINECODE10
3. Set INLINECODE11
4. Run mkdir -p to ensure both directories exist

When type = plan

1. 1. Read the latest .md file from INLINECODE15
2. If no plan file found, extract plan content from the current conversation context
3. Convert to Obsidian note format (see templates below)
4. Write Markdown to INLINECODE16
5. Write Canvas to INLINECODE17
6. Filename: [Plan] {title} ({YYYY-MM-DD}).md / INLINECODE19

When type = report

1. 1. Summarize the implementation work completed in the current session
2. Include: what was done, which files changed, key design decisions, follow-up TODOs
3. Convert to Obsidian note format
4. Write Markdown to INLINECODE21
5. Write Canvas to INLINECODE22
6. Filename: [Report] {title} ({YYYY-MM-DD}).md / INLINECODE24

Markdown Templates

Plan Template

CODEBLOCK2

Report Template

CODEBLOCK3

Canvas Sync (Dual Output)

Every Markdown sync also generates an Obsidian Canvas file (.canvas) for visual exploration.

Canvas Structure

Canvas is a JSON format with nodes (cards/groups) and edges (connections).

Report Canvas layout:

• - grp_summary (color:4 cyan) — Summary: title + date + 1-3 sentence overview
• INLINECODE29 (color:6 pink) — Completed work: split into sub-cards (steps, rules, etc.)
• INLINECODE30 (color:5 purple) — File changes: table of files and operations
• INLINECODE31 (color:3 green) — Design decisions: architecture/tech choices and rationale
• INLINECODE32 (color:2 orange) — Follow-up TODO: checklist of next steps

Plan Canvas layout:

• - grp_overview (color:4) — Plan overview and goals
• INLINECODE34 (color:6) — Implementation steps, one text node per step
• INLINECODE35 (color:3) — Architecture/tech decisions
• INLINECODE36 (color:2) — Risks and considerations

Layout principles:

• - Groups connected by edges showing flow direction
• Top-left start: Summary → Work/Steps → Files/Architecture → TODO
• Color key: 1=red, 2=orange, 3=green, 4=cyan, 5=purple, 6=pink

Sizing rules (prevent content clipping):

• - Text node min width 320px, recommended 500-660px
• Estimate 35px per line of text (including line spacing)
• Headers (##) at 45px, code blocks at 28px per line
• Text node height = line_count × 35 + 60 (top/bottom padding)
• Groups add 20px padding around contained text nodes
• Minimum 80px gap between groups (vertical and horizontal)
• Better too large than too small — clipping is worse than whitespace

Important Rules

1. 1. No YAML frontmatter — use > quote blocks for metadata instead
2. Quote blocks for metadata — date, source, status, project in > blocks
3. Preserve original plan content — never trim or rewrite technical details
4. Reports must be specific — list actual file paths, code patterns, design rationale
5. Always output both files — Markdown + Canvas on every sync
6. Report full paths — tell the user where both files were written
7. Auto-create directories — use mkdir -p if project or canvas dir doesn't exist

Auto-Sync Setup (Optional)

Add this to your project's CLAUDE.md to enable the full sync lifecycle:

CODEBLOCK4