obsidian-review — Claude Code command: weekly and monthly vault reports
obsidian-review — a command that generates a structured report of work completed over a week or month by reading daily notes, logs, projects, and task completion data from your Obsidian vault.
MIT ★ 5,412 updated 2026-10-24
/plugin marketplace add eugeniughelbur/obsidian-second-brain
/plugin install obsidian-second-brain@obsidian-second-brainWhat obsidian-review does
obsidian-review scans vault history—daily entries, dev logs, project statuses, completed tasks—and assembles a formatted report. The output includes sections for accomplishments, key decisions, collaborators, learning, and items to carry forward. Each report includes a block of 4–5 suggested questions for future agents, generated from vault content to surface contradictions between notes, connect unlinked entities, or flag unstated next steps.
The command uses a template from Templates/Review.md if present, otherwise falls back to a built-in structure. It reads _CLAUDE.md first to understand folder layout and context. The report is saved to the Reviews folder (or wiki/reviews, depending on vault config) and linked from the final daily note of the period.
Follows ai-first rules: every created note includes frontmatter with type, date, tags, and ai-first: true flag; all persons and projects linked via wikilinks; sources preserved verbatim. If references/ai-first-rules.md is not found, the command signals this before writing.
What it helps with
- compile a weekly report from scattered daily notes and project logs
- track status changes and shifts in goals across a period
- surface unanswered questions that vault content could address
- format a report with metadata and wikilinks for agent retrieval
- connect isolated facts from separate notes into one coherent view
Example prompts for the agent
- Generate my weekly review
- Create a monthly report from my Obsidian vault
- Review this week and build a structured report
How to install obsidian-review
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-review.mdCall it with /obsidian-review. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/obsidian-review.mdCall it with /prompts:obsidian-review. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/obsidian-review.prompt.mdManually: put the files in place
.gemini/commands/obsidian-review.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about obsidian-review
How do I install obsidian-review in Claude Code?
Run in order: /plugin marketplace add eugeniughelbur/obsidian-second-brain, then /plugin install obsidian-second-brain@obsidian-second-brain, then copy .claude/commands/obsidian-review.md to your project's commands folder.
What does obsidian-review do?
It collects daily notes, logs, projects, and completed tasks over a week or month, then writes a report with accomplishments, decisions, people involved, learning, and suggested follow-up questions for deeper exploration.
What vault files does obsidian-review need to work?
Daily notes, projects folder, and kanban boards (if present). Optional: _CLAUDE.md for folder mapping, Templates/Review.md for custom report layout, and references/ai-first-rules.md for frontmatter rules.
Source text
obsidian-review.md · MIT
--- description: Generate a structured weekly or monthly review note from vault history category: thinking triggers_en: ["weekly review", "monthly review", "review my week", "review my month"] triggers_de: ["Wochenrückblick", "Monatsrückblick", "meine Woche durchgehen", "meinen Monat durchgehen"] triggers_es: ["revisión semanal", "revisión mensual", "revisa mi semana", "revisa mi mes"] triggers_pt: ["revisão semanal", "revisão mensal", "revise minha semana", "revise meu mês"] triggers_zh: ["做每周复盘", "做月度复盘", "回顾我这一周的表现", "生成本月复盘"] --- Use the obsidian-second-brain skill. Execute `/obsidian-review $ARGUMENTS`: The optional argument specifies `weekly` or `monthly`. Ask if not clear from context. 1. Read `_CLAUDE.md` first if it exists in the vault root 2. Determine the period: weekly or monthly 3. Read daily notes and dev logs for the period 4. Read active projects and check for status changes 5. Read completed tasks from kanban boards 6. Draft a review note using `Templates/Review.md` (or lowercase `templates/Review.md`) if one exists, otherwise use: - What I accomplished - Key decisions made - People I worked with - What I learned - What to carry forward - **Suggested questions for future agent** - 4 to 5 questions this period's vault content can answer that the user has not asked yet. Each question must cite at least one specific note (with `[[wikilink]]`). Prefer questions that surface contradictions across notes, connect entities that co-appeared without being explicitly linked, or name an unstated next action. Skip generic prompts the review section already covers. 7. Save to the reviews folder resolved per `references/folder-map.md` (read the vault's `_CLAUDE.md` Folder Map first; wiki-style `wiki/reviews/`, Obsidian-style `Reviews/`), named `YYYY-MM-DD - Weekly Review.md` (or Monthly) 8. Link from the last daily note of the period --- **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