Journal Obsidian
/obsidian-logUtilise le skill obsidian-second-brain. Exécute `/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:
- Read
_CLAUDE.mdfirst if it exists in the vault root - Infer the project from conversation context - search the vault if needed to find the right project note
- Read
Templates/Dev Log.md(orTemplates/Work Log.mdif it exists) - Fill in: date, project, what was worked on, problems encountered, decisions made, next steps - all inferred from the conversation
- Save to
Dev Logs/YYYY-MM-DD — Project Name.md - Inject a link into the project note's Recent Activity section
- 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.