Create a session log summarizing this coding session and update the project state.
Target Detection
Same as /explain: check $ARGUMENTS first, then classify based on what the session work was about (not just the working directory). Work on vault templates, skills, ~/.claude/ config, or general tooling -> use general. Project-specific code/features/bugs -> detect from working directory. Fallback to general.
Steps
- •Read the session template at
~/AIVault/_templates/session.md - •Create session log at
~/AIVault/projects/{project-slug}/sessions/YYYY-MM-DD.md(or~/AIVault/general/sessions/YYYY-MM-DD.md) If a file for today already exists, append a-Nsuffix - •Fill in YAML frontmatter
- •Review git log, files changed, and conversation context to fill in:
- •Goal of the session
- •What was done (with specifics)
- •Commits made
- •Issues encountered
- •State after session
- •Use full-path wiki-links with display names:
[[path/to/file|Display Name]] - •Add a
## Relatedsection with cross-links to related vault documents - •Update
~/AIVault/projects/{project-slug}/state/{slug}-status.mdwith fresh state- •Project examples:
sfdb-status.md,general-status.md
- •Project examples:
- •Update the relevant
{scope}-home.mdMOC
Formatting
Reference the obsidian-markdown skill for Obsidian-flavored markdown conventions.