obsidian-recap — Claude Code command: what it does, how to install
obsidian-recap summarizes Obsidian vault activity for today, the week, or the month. It uses parallel subagents to process daily notes, dev logs, and kanban tasks into a structured recap.
MIT ★ 5,412 updated 2026-10-24
/plugin marketplace add eugeniughelbur/obsidian-second-brain
/plugin install obsidian-second-brain@obsidian-second-brainWhat obsidian-recap does
The command accepts today, week, or month as an argument, defaulting to week. It first checks _CLAUDE.md in the vault root, then locates daily notes according to references/folder-map.md. It spawns individual subagents in parallel for each daily note, dev log, and finished kanban card to extract decisions, contacts, and ideas.
The final output is a narrative synthesis rather than a file dump. Every recap finishes with four to five suggested questions for future agent runs, each anchored to a specific note via a [[wikilink]].
If references/ai-first-rules.md cannot be located in the working directory or parent folders, the agent stops and reports the missing path before writing notes. Unknown values are explicitly marked as TBD instead of being invented.
What it helps with
- summarize daily notes and kanban cards across a chosen timeframe
- surface unresolved contradictions across project notes
- generate targeted follow-up prompts with
[[wikilink]]references - extract completed tasks and decisions without reading daily files manually
Example prompts for the agent
- /obsidian-recap week
- /obsidian-recap today
- /obsidian-recap month
How to install obsidian-recap
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-recap.mdCall it with /obsidian-recap. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/obsidian-recap.mdCall it with /prompts:obsidian-recap. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/obsidian-recap.prompt.mdManually: put the files in place
.gemini/commands/obsidian-recap.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about obsidian-recap
How to install obsidian-recap in Claude Code?
Add the plugin marketplace entry with /plugin marketplace add eugeniughelbur/obsidian-second-brain, then run /plugin install obsidian-second-brain@obsidian-second-brain.
What does obsidian-recap do?
It reviews your Obsidian vault over a specified period by running parallel subagents across daily notes and dev logs, synthesizing them into a narrative report.
What happens if required reference files are missing?
The command relies on references/ai-first-rules.md and references/folder-map.md. If it cannot resolve the rules file after searching upward, it reports the issue before creating or editing any notes.
Source text
obsidian-recap.md · MIT
---
description: Summarize a time period from the vault - today, week, or month
category: vault
triggers_en: ["recap today", "recap the week", "summarize the week", "month recap"]
triggers_de: ["heute zusammenfassen", "Wochenrückblick", "die Woche zusammenfassen", "Monatsrückblick"]
triggers_es: ["resumen de hoy", "resumen de la semana", "resume la semana", "resumen del mes"]
triggers_pt: ["recapitule hoje", "recapitule a semana", "resuma a semana", "recap do mês"]
triggers_zh: ["总结今天发生的事", "汇总本周记录", "总结这一周发生了什么", "生成本月摘要"]
---
Use the obsidian-second-brain skill. Execute `/obsidian-recap $ARGUMENTS`:
The argument is the period: `today`, `week`, or `month`. Default to `week` if not specified.
1. Read `_CLAUDE.md` first if it exists in the vault root
2. Determine the date range from the argument
3. List all daily notes in the range from the daily folder, resolved per `references/folder-map.md` (wiki-style `wiki/daily/`, Obsidian-style `Daily/`)
4. Spawn parallel subagents - one per daily note - to read and extract key points from each simultaneously
5. Also spawn parallel agents to read dev logs and completed kanban tasks from the same period
6. Synthesize all agent results: what was worked on, decisions made, people interacted with, tasks completed, ideas captured
7. Present as a clean narrative summary - not a raw dump of note content
8. End the recap with a **Suggested questions for future agent** section: 4 to 5 questions this period's vault content is uniquely positioned to answer that the user has not asked yet. Each question must cite at least one specific note (with `[[wikilink]]`) so future agent can resolve it without re-scanning. Prefer questions that:
- Surface tensions across notes (e.g., "Why does the X decision in [[note A]] contradict the rationale in [[note B]]?")
- Connect entities that co-appeared but were never explicitly linked
- Identify unstated next actions implied by the period's work
Avoid generic prompts ("What did I work on?") - the recap already answers those.
---
**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