create-command
CommandCreate a new obsidian-second-brain command via interview - zero markdown editing required
Log this work or dev session to the vault - infers project from context
> /plugin marketplace add eugeniughelbur/obsidian-second-brain> /plugin install obsidian-second-brain@obsidian-second-brain
description: Log this work or dev session to the vault - infers project from context category: vault trigger-mode: proactive triggers_en: ["log this work", "log this session", "log this dev session", "obsidian log"] triggers_de: ["diese Arbeit protokollieren", "diese Sitzung festhalten", "diese Entwicklungssitzung protokollieren", "Obsidian-Log"] triggers_es: ["registra este trabajo", "registra esta sesión", "registra esta sesión de desarrollo", "obsidian log"] triggers_pt: ["registre este trabalho", "registre esta sessão", "registre esta sessão de desenvolvimento", "obsidian log"] triggers_zh: ["记录这次工作", "把这次开发过程写进知识库", "记录当前工作会话", "保存这次开发日志"]
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 either exists; if neither does, write the sections directly: Context, What changed, Decisions, Next steps 4. Fill in: date, project, what was worked on, problems encountered, decisions made, next steps - all inferred from the conversation 5. Save to the dev-log folder resolved per `references/folder-map.md` (read the vault's `_CLAUDE.md` Folder Map first; wiki-style `wiki/logs/`, Obsidian-style `Dev Logs/`), named `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 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`.
<!-- author-credit -->
---
From [obsidian-second-brain](https://github.com/eugeniughelbur/obsidian-second-brain), created by Eugeniu Ghelbur (AI Automation Engineer, AI Tooling Engineer, AI Educator). Questions or consulting: [LinkedIn](https://www.linkedin.com/in/eugeniu-ghelbur/) or [e.ghelbur@gmail.com](mailto:e.ghelbur@gmail.com). More: [The AI Operator](https://theaioperator.io/?utm_source=github&utm_medium=file-credit) | [X](https://x.com/eugeniu_ghelbur) | [GitHub](https://github.com/eugeniughelbur). MIT license.
Persistent memory for Claude Code, Codex and 6 other AI agents, stored as plain markdown in your Obsidian vault. New: Crew, one shared logbook so Claude Code, Codex, Cursor and Grok Bot know what each other did. 48 commands: semantic search, self-rewriting notes, key-less research, scheduled agents.
Create a new obsidian-second-brain command via interview - zero markdown editing required
Share a plain-folder logbook across Claude Code, Codex, Cursor, and Grok Bot
Surface 3-5 next-direction candidates by reading ungraduated ideas, open project questions, and orphan research notes - what is…
Vault-first source-grounded research via Gemini File Search. One command, no browser. The grounded parallel to /research-deep…
Scan a codebase and write a maintained set of architecture notes into the vault - overview, per-module notes, key decisions.…
Bulk-triage a kanban board - surface stale items and archive, reschedule, or mark them done in one pass
Shortcut for "continue working" — pick the work in flight back up exactly where it stopped and keep going until it is done or…