Skip to main content
command CX Codex

obsidian-reconcile — Claude Code command

obsidian-reconcile is a Claude Code command that finds contradictions in an Obsidian vault and resolves them automatically or flags them for review. It scans the full vault or a specific topic.

MIT ★ 5,412 updated 2026-10-24

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add eugeniughelbur/obsidian-second-brain
/plugin install obsidian-second-brain@obsidian-second-brain
Open on GitHub

What obsidian-reconcile does

Works within Claude Code. The command searches for contradictions across four dimensions: factual claims in concepts and projects folders, outdated roles or descriptions in entities, reversed or superseded decisions, and source dates in raw/ versus wiki/ sections.

Each found contradiction is verified—two quotes are pulled from different notes, a script confirms both exist at their stated line and path. Once verified, the command ranks which source is fresher and more authoritative. Contradictions are resolved three ways: the outdated note is rewritten with a History section showing what changed, genuinely ambiguous cases are moved to a Conflict note for human judgment, or the shift is recognised as evolution—someone changed their mind, and that's recorded in context.

Requires vault structure: a references/ folder with folder-map.md and ai-first-rules.md files. Logs append to Logs/YYYY-MM-DD.md or log.md. All new and modified notes follow AI-first rules: frontmatter with type, date, tags, wikilinks, and inline sources.

What it helps with

  • locate contradictory statements across multiple notes
  • update stale facts based on fresher sources
  • find reversed decisions that were never removed from other sections
  • document genuinely disputed claims when neither source clearly wins

Example prompts for the agent

  • Find all contradictions in my vault /obsidian-reconcile
  • Check for conflicts about architecture /obsidian-reconcile architecture
  • Verify company descriptions for inconsistencies /obsidian-reconcile entities

How to install obsidian-reconcile

1Plugin marketplace

/plugin marketplace add eugeniughelbur/obsidian-second-brain
/plugin install obsidian-second-brain@obsidian-second-brain

2Manually: put the files in place

.claude/commands/obsidian-reconcile.md

Call it with /obsidian-reconcile. For all projects use ~/.claude/commands/

Questions about obsidian-reconcile

How do I install obsidian-reconcile in Claude Code?

Run in order: /plugin marketplace add eugeniughelbur/obsidian-second-brain, then /plugin install obsidian-second-brain@obsidian-second-brain, then create .claude/commands/obsidian-reconcile.md with the command configuration.

What does obsidian-reconcile do?

It identifies contradictions in your Obsidian vault—different versions of the same fact across notes—and either automatically rewrites notes to match the fresher source or creates a conflict note for you to decide.

What vault structure do I need?

You need a references/ folder containing folder-map.md (which maps your folder layout) and ai-first-rules.md (formatting rules for new notes), plus _CLAUDE.md and index.md at the root. Logs go to Logs/ or log.md in the root.

Source text

obsidian-reconcile.md · MIT
---
description: Find and resolve contradictions in the vault - the vault maintains its own truth
category: thinking
triggers_en: ["find contradictions", "reconcile vault", "fix conflicts", "vault contradictions"]
triggers_de: ["Widersprüche finden", "Vault abgleichen", "Konflikte lösen", "Widersprüche im Vault"]
triggers_es: ["busca contradicciones", "concilia el vault", "resuelve los conflictos", "contradicciones en el vault"]
triggers_pt: ["encontre contradições", "reconcilie o vault", "corrija conflitos", "contradições do vault"]
triggers_zh: ["找出知识库里的矛盾", "解决笔记之间的冲突", "核对相互矛盾的说法", "让知识库里的事实保持一致"]
---

Use the obsidian-second-brain skill. Execute `/obsidian-reconcile $ARGUMENTS`:

The optional argument is a topic or entity to focus on. If not provided, scan the whole vault.

1. Read `_CLAUDE.md` first if it exists in the vault root
2. Read `index.md` to understand the full vault landscape

3. Spawn parallel subagents to find contradictions:
   - **Claims agent**: scan the concepts and projects folders (resolved per `references/folder-map.md`) for factual claims - find pairs that contradict each other
   - **Entity agent**: scan the entities folders (resolved per `references/folder-map.md`, which gives Obsidian-style vaults a separate folder for some entity kinds) for outdated roles, companies, or descriptions that conflict with newer sources
   - **Decisions agent**: scan the decisions folder (resolved per `references/folder-map.md`) and project Key Decisions for reversed or superseded decisions that were never updated
   - **Source freshness agent**: compare `raw/` source dates against `wiki/` page dates - flag wiki pages that reference old sources when newer ones exist on the same topic

   The claims, entity and decisions agents return each contradiction as two claims, one per side. Each claim has the note's vault-relative `path`, the `line` number, and a `quote`: one line copied character for character from that note, at least 12 characters long. A contradiction without both quotes is not a finding. Pass this format to every subagent.

4. Prove each contradiction before acting on it. Send both claims to the checker (the skill root's absolute path was given at session start as **Skill root**; substitute it for `SKILL_ROOT`):

   ```bash
   uv run --directory "SKILL_ROOT" scripts/verify_quotes.py --path <vault> <<'EOF'
   [{"path": "<note path>", "line": 12, "quote": "<line copied from that note>"},
    {"path": "<other note path>", "line": 40, "quote": "<line copied from that note>"}]
   EOF
   ```

   - Both claims must come back `"ok": true`. If either fails, drop the contradiction: no rewrite, no conflict note. List it under **Dropped as unproven** with the `reason` the checker gave.
   - Use `found_line` from the output, not the line the subagent gave.
   - Source freshness findings compare dates, not claims, so they skip this step.

   For each proven contradiction, evaluate:
   - **Which source is newer?** (date comparison)
   - **Which source is more authoritative?** (peer-reviewed > blog post > transcript > opinion)
   - **Is this a genuine contradiction or an evolution?** (someone changing their mind is not a contradiction - it's growth)

5. Resolve each contradiction:
   - **Clear winner**: rewrite the outdated page with current info. Add a `## History` section noting what changed and why, with the proven quote it replaced: "Previously stated X (source: raw/articles/old-article.md, 2025-11-01). Updated to Y based on newer evidence (source: raw/articles/new-article.md, 2026-03-15)."
   - **Genuinely ambiguous**: create `Conflict - Topic.md` in the decisions folder (resolved per `references/folder-map.md`; `type: conflict`, schema in `references/ai-first-rules.md`) documenting both sides with their verbatim quotes and `path:line`, the evidence for each, and mark as `status: open` for the user to decide
   - **Evolution**: update the entity/concept page to reflect the current state and add the historical context

6. After all resolutions:
   - Rebuild affected sections of `index.md`
   - Append to the operation log: if `Logs/` exists write `**HH:MM** - reconcile | X contradictions reported, P proven, D dropped as unproven, Y auto-resolved, Z flagged for user` to `Logs/YYYY-MM-DD.md`; otherwise append `## [YYYY-MM-DD] reconcile | X contradictions reported, P proven, D dropped as unproven, Y auto-resolved, Z flagged for user` to `log.md`
   - Update today's daily note with a reconciliation summary

7. Report back:
   - **Auto-resolved** (list with old claim → new claim and why)
   - **Flagged for user** (genuinely ambiguous - needs human judgment)
   - **Stale pages updated** (pages rewritten with fresher sources)
   - **Dropped as unproven** (each claim, its `path`, and the checker's `reason`)

The vault should never contain two pages that disagree without knowing they disagree. Contradictions are either resolved or explicitly documented as open questions. A contradiction nobody can quote is not resolved at all: rewriting a note to fix a disagreement that is not there puts a new error into the vault.

---

**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

Similar slash commands

All slash commands for Notes, tasks and projects →

From the same set51

The whole set →
obsidian-brainstorm obsidian-brainstorm is a Claude Code command that interviews you about an idea one question at a time, then writes a design note with alternatives and a recommendation. CX Codex +1 ★ 5,412repo stars podcast Extracts podcast episode metadata, transcript, and structured summary directly into an Obsidian vault note. CX Codex +1 ★ 5,412repo stars youtube Pulls a YouTube transcript, metadata, and top comments into an Obsidian note. Add --visual when the video’s frames matter too. CX Codex +1 ★ 5,412repo stars obsidian-architect obsidian-architect scans a project and generates architecture notes in your vault: overview with diagram, per-module notes, key decisions. Re-run to refresh docs without losing your edits. CX Codex +1 ★ 5,412repo stars obsidian-visualize The obsidian-visualize command maps your Obsidian vault visually: shows how notes connect, identifies hubs, and highlights isolated entries. Use it to see your second brain's shape at a glance. CX Codex +1 ★ 5,412repo stars obsidian-distill obsidian-distill condenses a long note or article into key claims, each tagged with the exact source block it came from — paragraph, section, or timestamp. CX Codex +1 ★ 5,412repo stars obsidian-merge obsidian-merge merges near-duplicate Obsidian notes without deleting files. It preserves links, unions frontmatter, and converts the retired note into a redirect stub. CX Codex +1 ★ 5,412repo stars obsidian-checkin The obsidian-checkin command asks the vault owner to confirm aging facts in notes and records their replies. Use it to review details about people or projects that may have changed. CX Codex +1 ★ 5,412repo stars

Project sponsors

Companies that keep this analytics open