Use when the user invokes /done to save the current session context to their Obsidian vault as a structured markdown file
Export the current conversation context — decisions, problems, solutions, files changed, and follow-ups — into a structured Obsidian markdown file.
When /done is invoked, execute these steps in order:
Run these commands to collect metadata:
# Get branch name (fallback for detached HEAD)
git branch --show-current || git rev-parse --short HEAD
# Get project name from directory basename
basename "$(pwd)"
# Generate session ID timestamp
date +%Y%m%dT%H%M%S
# Get current date
date +%Y-%m-%d
Build the tags array automatically:
claude-session, <project-name>NPR-615 from NPR-615-1-be-fetch-all-the-unrated-learners-of-a-test).ts files or NestJS patterns → typescript, nestjs.tsx/.jsx or React patterns → react.prisma or Prisma usage → prisma.py files → pythondevopstestingReview the ENTIRE conversation and write each section. Be thorough but concise — capture the essential context someone would need to pick up this work later.
Title: Write a short, descriptive title summarizing the session's main accomplishment or topic.
Summary paragraph: 2-3 sentences describing what was done, the approach taken, and current state.
Sections to include (omit any section that has no content):
- **Decision label**: Explanation of what was decided and why.- \path/to/file.ts` — Description of change (STATUS)`- [ ] Action item descriptionUse this exact template structure:
---