vault-deep-synthesis — Claude Code command: what it does, install
The vault-deep-synthesis command reads every vault note tied to a topic and produces a synthesis of agreements, conflicts, aging claims, and unanswered questions.
MIT ★ 5,412 updated 2026-10-24
/plugin marketplace add eugeniughelbur/obsidian-second-brain
/plugin install obsidian-second-brain@obsidian-second-brainWhat vault-deep-synthesis does
vault-deep-synthesis takes a topic and searches the vault across its actual top-level folders. It checks names, aliases, and folder context, then reads every matching note. The resulting view separates claims supported by several notes, disagreements between notes, facts that may have gone stale, and questions the vault cannot answer. Source notes are linked with [[wikilinks]].
The command writes YYYY-MM-DD - synthesis - <topic-slug>.md into the concepts folder resolved through references/folder-map.md. The file includes synthesis metadata and the notes that were read; a one-line operation-log entry is added, while source notes stay untouched. Before writing, the command follows references/ai-first-rules.md. If that file cannot be read, it reports the issue before creating the note.
This is a vault-only workflow: it uses no network connection and needs no API key. Exhaustive matching matters here, since a partial scan presented as complete would distort the result.
What it helps with
- compile a topic brief from every related vault note
- compare claims that appear across separate notes
- surface conflicts without resolving them
- flag aging facts and unanswered questions
Example prompts for the agent
- Synthesize everything my vault knows about
topic. - Cross-reference my notes on
topicand save the result. - What does my vault say about
topic? Show agreements, contradictions, stale claims, and gaps.
How to install vault-deep-synthesis
1Plugin marketplace
/plugin marketplace add eugeniughelbur/obsidian-second-brain/plugin install obsidian-second-brain@obsidian-second-brain2Manually: put the files in place
.claude/commands/vault-deep-synthesis.mdCall it with /vault-deep-synthesis. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/vault-deep-synthesis.mdCall it with /prompts:vault-deep-synthesis. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/vault-deep-synthesis.prompt.mdManually: put the files in place
.gemini/commands/vault-deep-synthesis.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about vault-deep-synthesis
How do I install vault-deep-synthesis in Claude Code?
Add the marketplace with /plugin marketplace add eugeniughelbur/obsidian-second-brain, then install the plugin with /plugin install obsidian-second-brain@obsidian-second-brain.
What does vault-deep-synthesis do?
It scans the vault for notes related to a named topic, compares their claims, and writes a synthesis covering agreement, conflict, stale information, and missing coverage.
Does it edit source notes or use the network?
It leaves source notes unchanged and works entirely from the vault. Network access and API keys are not required.
Source text
vault-deep-synthesis.md · MIT
--- description: Deep cross-reference of everything the vault knows about one topic - agreements, contradictions, stale claims, and coverage gaps. Pure vault, no network category: thinking triggers_en: ["synthesize what I know about", "deep synthesis on", "cross-reference my notes on", "what does my vault say about"] triggers_de: ["synthesiere, was ich über ... weiß", "tiefe Synthese zu", "meine Notizen zu ... abgleichen", "was sagt mein Vault über"] triggers_es: ["sintetiza lo que sé sobre", "síntesis profunda sobre", "cruza mis notas sobre", "qué dice mi vault sobre"] triggers_pt: ["sintetize o que eu sei sobre", "síntese profunda sobre", "cruze minhas notas sobre", "o que meu vault diz sobre"] triggers_zh: ["综合知识库里关于这个主题的一切", "深度梳理我对这个主题的笔记", "交叉核对这个主题的所有记录", "我的知识库对这个主题怎么说"] --- Use the obsidian-second-brain skill. Execute `/vault-deep-synthesis [topic]`: A focused, topic-driven cross-reference of the existing vault. Unlike `/obsidian-synthesize` (which scans the whole vault for unnamed patterns unprompted), this takes a topic you name and reads every note touching it to produce one consolidated view. Pure vault: no network, no API keys. 1. Resolve the topic from the argument. If none, ask what to synthesize. 2. Find every note that references the topic - grep and list exhaustively across whatever top-level note folders the vault actually has (read the vault root once; typically `wiki/`, `Research/`, and any project/concept folders named in `_CLAUDE.md` per `references/folder-map.md` - do not assume a fixed list, do not sample; see the anti-fabrication rule). Match by every plausible name, alias, and folder. 3. Read the matching notes and cross-reference them into: - **What the vault agrees on** - claims multiple notes corroborate, with `[[wikilinks]]` to each. - **Contradictions** - where notes disagree; name both `[[notes]]` and the specific conflict. Do not resolve them here (that is `/obsidian-reconcile`); just surface them. - **Stale claims** - dated facts that may no longer hold (cite the note and the date). - **Coverage gaps** - questions the topic raises that the vault does not answer. 4. Write the synthesis to the concepts folder (resolved per `references/folder-map.md` - wiki-style `wiki/concepts/`, Obsidian-style `Ideas/`) as `YYYY-MM-DD - synthesis - <topic-slug>.md` (`type: synthesis`, tagged `[research, thinking, vault-deep-synthesis]`), listing the source notes it read in frontmatter. 5. Do NOT modify the source notes - this command only reads and synthesizes. Append a one-line entry to the operation log. --- **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:** Enumerate the matching notes exhaustively, do not sample - a partial scan reported as complete produces confident wrong answers. Never invent a claim, contradiction, or source; if the vault is thin on the topic, say so. See the anti-fabrication and search-completeness hard rules in `references/ai-first-rules.md`.
© Eugeniu Ghelbur · MIT · eugeniughelbur/obsidian-second-brain