Session Summary
When a Claude Code session ends, this skill systematically organizes what files were modified, what was completed, and what needs to be continued in the next session.
/summaryDeveloper juggling multiple sessions a day? Run /summary before leaving to hand off context to your future self
Team lead sharing progress updates? Share session summaries directly to Slack
How It Works
Skill Code
Copy and paste into your CLAUDE.md to start using immediately.
How Session Summary Works
Session Summary scans your working directory for modified files, classifies each change as completed or in-progress, and compiles a date-stamped summary with an auto-generated next-steps list — all in a single /summary command.
When to Use Session Summary
Most valuable at the end of a long coding session when you need to hand off context to your future self or share a concise progress update with teammates on Slack or in a stand-up.
Key Strengths
- Automatically detects file changes without manual tracking
- Separates completed tasks from work-in-progress items
- Generates actionable next-steps you can pick up immediately
- Date-stamped output perfect for daily stand-ups and async updates