Obsidian log
/obsidian-logUse the obsidian-second-brain skill. Execute `/obsidian-log`:
--- description: Log this work or dev session to the vault - infers project from context category: vault triggers_en: ["log this work", "log this session", "log this dev session", "obsidian log"] --- Use the obsidian-second-brain skill. Execute /obsidian-log: 1. First, read _CLAUDE.md if it exists in the Vault root 2. Infer the project from the conversation context:search the Vault if necessary to find the correct 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. Insert a link into the project note’s “Recent Activity” section 7. Insert a link into the “Work” section of today’s daily note --- 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-Clauderetrieval:not for human reading. Anti-fabrication: Search exhaustively before claiming that any note, person, or file is missing:false absence is the most common failure mode:and never invent facts, entities, or dates (mark unknowns as “TBD”). See the hard rules on anti-fabrication and search completeness at references/ai-first-rules.md.