← ClaudeAtlas

obsidian-loglisted

Write a session log entry to the Obsidian vault for the current Claude Code session. Use when someone says "log this session", "save session to Obsidian", "obsidian log", "write a session note", "log what we did", "record what we built". Gathers git context and asks for a brief summary before writing. Requires OBSIDIAN_VAULT_PATH to be set.
chuckplayer/claude-agent-pack · ★ 2 · AI & Automation · score 75
Install: claude install-skill chuckplayer/claude-agent-pack
# Obsidian Log Write a lightweight session log capturing what was built, any decisions made, and what comes next. Session logs land in the project's vault folder (`<projects_folder>/<repo>/sessions/` or `Claude/<repo>/sessions/` if no projects folder is configured) and are linked into the daily note automatically. ## Step 1 — Check configuration Read `OBSIDIAN_VAULT_PATH` from the environment: - Bash: `bash -c 'echo $OBSIDIAN_VAULT_PATH'` - PowerShell: `$env:OBSIDIAN_VAULT_PATH` If empty, stop and tell the user: > "OBSIDIAN_VAULT_PATH is not set. Re-run `install.sh` and provide your vault > path when prompted, or add it manually to `~/.claude/settings.json` under > the `env` key." Also read: - `OBSIDIAN_REST_API_KEY` (empty string if unset — key presence gates REST API use) - `OBSIDIAN_REST_API_PORT` (default `27124` if unset) - `OBSIDIAN_REST_API_HTTPS` (default `"true"` if unset) - `OBSIDIAN_PROJECTS_FOLDER` (empty string if unset) ## Step 2 — Gather git context Run these commands via the Bash tool: - `git branch --show-current` — current branch name - `git log --oneline -5` — five most recent commits - `git diff --stat HEAD~1 2>/dev/null || echo "(no prior commit)"` — files changed in the last commit - Current datetime (record at the moment of invocation) ## Step 3 — Ask for summary Ask the user: > "What were the key things done, any decisions made, and what's next? A few > bullets is all that's needed — this is lightweight." Accept the user's response as-is