| name | summarize-session |
| description | Capture a structured session work journal — what was built, decisions made, current state, and next steps. Writes to project memory for future session context. |
Summarize Session Skill
Captures the narrative of a development session as a persistent work journal. Distinct from auto-memory (which records stable patterns/conventions) — this records what happened, what was decided, and what to pick up next.
When to Use
- End of a development session before closing the conversation
- After completing a significant chunk of work
- Manual invocation with
/summarize-session
Behavior
- Non-interactive: Scans context, writes file, prints summary — no prompts
- Persistent: Writes to project memory so future sessions have context
- Additive: Appends if a summary for today already exists
Instructions
CRITICAL — NON-INTERACTIVE: Run every step to completion without pausing. Never ask questions, request confirmation, offer choices, or wait for input. Scan, write, and report.
Step 1: Gather Context
Review the conversation history to understand what was done this session. Also run:
git log --oneline -20
git diff --stat HEAD
git status --short
Step 2: Compose Summary
Based on the conversation context and git data, write a structured summary. Be concrete and specific — future sessions should be able to pick up exactly where this one left off.
