obsidian-synthesize — Claude Code command
obsidian-synthesize — a Claude Code command that scans your Obsidian vault for unnamed patterns and automatically generates synthesis pages without prompting. Discovers connections between ideas you may have missed.
MIT ★ 5,412 updated 2026-10-24
/plugin marketplace add eugeniughelbur/obsidian-second-brain
/plugin install obsidian-second-brain@obsidian-second-brainWhat obsidian-synthesize does
The command runs as a standalone agent: it reads your vault structure, spawns four parallel search subagents, and writes synthesis pages directly to your concepts folder. It finds cross-source patterns where the same concept appears in a podcast transcript, article, and daily note simultaneously; tracks how ideas you've edited three or more times have evolved; identifies people appearing together across multiple contexts without an explicit connection page; rescues orphaned notes that contain claims belonging to existing pages but lack incoming links.
Each synthesis page receives frontmatter with date and tags, links back to source notes, and explains what the pattern reveals. Results are logged to your operation journal. The command works with folder structures defined in references/folder-map.md and enforces references/ai-first-rules.md standards for all new notes: type identification, confidence markers, wikilinks for every person and concept, sources preserved with inline URLs.
Before running, verify that index.md and _CLAUDE.md at your vault root are current — the command uses them for its initial pass.
What it helps with
- uncover hidden connections between ideas across different sources
- track how your understanding of a concept changed over time
- find people and projects that interweave across multiple contexts
- identify important notes lost without incoming links
- generate overview synthesis pages automatically without manual work
Example prompts for the agent
- /obsidian-synthesize
- synthesize my vault and find new patterns
- run auto-synthesis to create overview notes
How to install obsidian-synthesize
1Plugin marketplace
/plugin marketplace add eugeniughelbur/obsidian-second-brain/plugin install obsidian-second-brain@obsidian-second-brain2Manually: put the files in place
.claude/commands/obsidian-synthesize.mdCall it with /obsidian-synthesize. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/obsidian-synthesize.mdCall it with /prompts:obsidian-synthesize. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/obsidian-synthesize.prompt.mdManually: put the files in place
.gemini/commands/obsidian-synthesize.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about obsidian-synthesize
How do I install obsidian-synthesize in Claude Code?
In Claude Code, run /plugin marketplace add eugeniughelbur/obsidian-second-brain, then /plugin install obsidian-second-brain@obsidian-second-brain. Copy the command file to .claude/commands/obsidian-synthesize.md in your project root.
What does obsidian-synthesize do?
It scans your Obsidian vault for unnamed patterns: concepts appearing across unrelated sources, how your thinking on ideas has evolved, implicit relationships between people, and notes without incoming links. It creates synthesis pages explaining each discovery.
What folder structure does obsidian-synthesize require?
The command expects the structure described in references/folder-map.md. At minimum: concepts, entities, sources, and either a Logs folder or log.md for the operation journal. It scans raw/ for sources from the last seven days.
Source text
obsidian-synthesize.md · MIT
---
description: Automatic synthesis - scans the vault for unnamed patterns and writes synthesis pages without being asked
category: thinking
triggers_en: ["synthesize", "auto-synthesis", "make synthesis notes", "find unnamed patterns"]
triggers_de: ["synthetisieren", "automatische Synthese", "Synthesenotizen erstellen", "unbenannte Muster finden"]
triggers_es: ["sintetiza", "síntesis automática", "crea notas de síntesis", "busca patrones nuevos", "saca conclusiones de mis notas"]
triggers_pt: ["sintetize", "auto-síntese", "crie notas de síntese", "encontre padrões sem nome"]
triggers_zh: ["自动综合我的知识库", "生成综合笔记", "把未命名的模式写成总结", "扫描知识库并形成综合结论"]
---
Use the obsidian-second-brain skill. Execute `/obsidian-synthesize`:
This command can run manually or as a scheduled agent. It thinks for you.
1. Read `_CLAUDE.md` first if it exists in the vault root
2. Read `index.md` to understand all existing pages
3. Read recent operation log: if `Logs/` exists, read the last 2-3 `Logs/YYYY-MM-DD.md` files; otherwise read `log.md` (last 20 entries)
4. Scan for synthesis opportunities - spawn parallel subagents:
- **Cross-source agent**: read all sources ingested in the last 7 days (`raw/`). Find concepts that appear in 2+ unrelated sources. If the same idea shows up in a podcast transcript AND an article AND a daily note - that's a synthesis candidate.
- **Entity convergence agent**: scan the entities folder (resolved per `references/folder-map.md`) for people who appear together in multiple contexts but have no explicit connection page. If Person A and Person B keep showing up in the same projects/decisions - write a connection note.
- **Concept evolution agent**: scan the concepts folder (resolved per `references/folder-map.md`) for ideas that have been updated 3+ times. Track how the concept evolved - write a "Concept Evolution" section showing the timeline of how the user's thinking changed.
- **Orphan rescue agent**: find notes in any note folder (enumerate the folders present, per `references/folder-map.md`) with no incoming links that contain claims or ideas that SHOULD be linked to existing pages. Create the missing links and explain why.
5. For each synthesis found:
- Create `Synthesis - Title.md` in the concepts folder (resolved per `references/folder-map.md`) with:
```yaml
---
date: YYYY-MM-DD
tags:
- concept
- synthesis
auto_generated: true
---
```
- Document: what pattern was found, which sources/notes it came from (with links), what it means, and a suggested action
- Link the synthesis page FROM all the source notes it references
6. Update `index.md` with new synthesis pages
7. Append to the operation log: if `Logs/` exists write `**HH:MM** - synthesize | X synthesis pages created, Y orphans rescued, Z connections found` to `Logs/YYYY-MM-DD.md`; otherwise append `## [YYYY-MM-DD] synthesize | X synthesis pages created, Y orphans rescued, Z connections found` to `log.md`
8. If a daily note exists for today, add a Synthesis section with a brief summary
The vault should generate its own insights. Not just when asked - on its own schedule.
---
**AI-first rule:** Every note created or updated by this command MUST follow `references/ai-first-rules.md` - `## For future agent` preamble, rich frontmatter (`type`, `date`, `tags`, `ai-first: true`, plus type-specific fields), recency markers per external claim, mandatory `[[wikilinks]]` for every person/project/concept referenced, sources preserved verbatim with URLs inline, and confidence levels where applicable. If that path does not resolve from your working directory, search upward for it; if you still cannot read it, say so before writing rather than producing a note that silently skips the rule. The vault is for future agent retrieval - not human reading.
**Anti-fabrication:** Search exhaustively before claiming any note, person, or file is absent - false absence is the most common failure mode - and never invent facts, entities, or dates (mark unknowns as `TBD`). See the anti-fabrication and search-completeness hard rules in `references/ai-first-rules.md`.
© Eugeniu Ghelbur · MIT · eugeniughelbur/obsidian-second-brain