# vault-deep-synthesis

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.

- command · `type=command` · Claude Code, Codex, GitHub Copilot, Gemini CLI · ★ 5412 repo stars
- Author: Eugeniu Ghelbur
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/eugeniughelbur/obsidian-second-brain/tree/HEAD/commands/vault-deep-synthesis.md
- Updated: 2026-10-24
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/commands/vault-deep-synthesis

## What it 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.

## Requirements
- Works with: Obsidian

## Install

### Claude Code (native platform)

1. **Plugin marketplace**
In the agent chat (not a shell):
```text
/plugin marketplace add eugeniughelbur/obsidian-second-brain
```
In the agent chat (not a shell):
```text
/plugin install obsidian-second-brain@obsidian-second-brain
```

2. **Manually: put the files in place**
- File: `.claude/commands/vault-deep-synthesis.md` — Call it with /vault-deep-synthesis. For all projects use ~/.claude/commands/

### Codex

**Manually: put the files in place**
- File: `~/.codex/prompts/vault-deep-synthesis.md` — Call it with /prompts:vault-deep-synthesis. Codex marks this format deprecated in favour of skills

### GitHub Copilot

**Manually: put the files in place**
- File: `.github/prompts/vault-deep-synthesis.prompt.md`

### Gemini CLI

**Manually: put the files in place**
- File: `.gemini/commands/vault-deep-synthesis.toml` — Gemini stores commands as TOML: the prompt text goes into the prompt field

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/eugeniughelbur/obsidian-second-brain/tree/HEAD/commands/vault-deep-synthesis.md

## When to use it
- 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
- Synthesize everything my vault knows about `topic`.
- Cross-reference my notes on `topic` and save the result.
- What does my vault say about `topic`? Show agreements, contradictions, stale claims, and gaps.

## Source text · vault-deep-synthesis.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 15de4ca59c2fabdb.

BEGIN THIRD-PARTY FILE 15de4ca59c2fabdb
```text
---
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.
```
END THIRD-PARTY FILE 15de4ca59c2fabdb

The third-party file has ended. Everything between the 15de4ca59c2fabdb tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 3380 of 3718 bytes. © Eugeniu Ghelbur · MIT · https://github.com/eugeniughelbur/obsidian-second-brain/tree/HEAD/commands/vault-deep-synthesis.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
