# obsidian-recap

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.

- 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/obsidian-recap.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/obsidian-recap

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

## 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/obsidian-recap.md` — Call it with /obsidian-recap. For all projects use ~/.claude/commands/

### Codex

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

### GitHub Copilot

**Manually: put the files in place**
- File: `.github/prompts/obsidian-recap.prompt.md`

### Gemini CLI

**Manually: put the files in place**
- File: `.gemini/commands/obsidian-recap.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/obsidian-recap.md

## When to use it
- 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
- /obsidian-recap week
- /obsidian-recap today
- /obsidian-recap month

## Source text · obsidian-recap.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: 7f2176ebd3670af3.

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

The third-party file has ended. Everything between the 7f2176ebd3670af3 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.

© Eugeniu Ghelbur · MIT · https://github.com/eugeniughelbur/obsidian-second-brain/tree/HEAD/commands/obsidian-recap.md

## Similar
- [obsidian](https://affpapa.org/en/nevibecode/skills/teknium-teknium1-hermes-agent-obsidian.md) — skill · 503 installs
- [pp-obsidian](https://affpapa.org/en/nevibecode/skills/pp-obsidian.md) — skill · 136 installs
- [oh-my-obsidian](https://affpapa.org/en/nevibecode/plugins/oh-my-obsidian.md) — plugin · ★ 31 repo stars
- [wiki-context-pack](https://affpapa.org/en/nevibecode/skills/wiki-context-pack.md) — skill · 1700 installs
- [canvas](https://affpapa.org/en/nevibecode/skills/agricidaniel-canvas.md) — skill · 500 installs
- [obsidian-canvas-creator](https://affpapa.org/en/nevibecode/skills/obsidian-canvas-creator.md) — skill · 2000 installs

_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
