Skip to main content
ClaudeWave
Slash Command2.4k repo starsupdated today

obsidian-log

The obsidian-log command automatically creates a timestamped dev or work log entry in an Obsidian vault by inferring the active project from conversation context, populating structured fields like problems and next steps, and cross-linking the entry into the project note and daily log. Use it at the end of a development or work session to capture session notes without manual organization.

Install in Claude Code
Copy
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/eugeniughelbur/obsidian-second-brain/HEAD/commands/obsidian-log.md -o ~/.claude/commands/obsidian-log.md
Then start a new Claude Code session; the slash command loads automatically.

obsidian-log.md

Use the obsidian-second-brain skill. Execute `/obsidian-log`:

1. Read `_CLAUDE.md` first if it exists in the vault root
2. Infer the project from conversation context - search the vault if needed to find the right project note
3. Read `Templates/Dev Log.md` (or `Templates/Work Log.md` if it exists)
4. Fill in: date, project, what was worked on, problems encountered, decisions made, next steps - all inferred from the conversation
5. Save to `Dev Logs/YYYY-MM-DD — Project Name.md`
6. Inject a link into the project note's Recent Activity section
7. Inject a link into today's daily note Work section

---

**AI-first rule:** Every note created or updated by this command MUST follow `references/ai-first-rules.md` - `## For future Claude` 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. The vault is for future-Claude 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`.