Quick Example
/skill:session:end # Output: # Session: 2026-01-27-1430-fyp-interim-report # Duration: 2h 45m # Git changes: 3 files, 2 commits # Tasks completed: 6/8 # Session archived
Session End Context
End Time: !date '+%Y-%m-%d %H:%M:%S'
Active Session: !cat .claude/sessions/.current-session 2>/dev/null || echo "None"
Final Git Status: !git status --short 2>/dev/null || echo "Not in git repo"
TODO Summary: !cat TODO.md 2>/dev/null || echo "No TODO.md"
End the current development session by:
- •
Check
.claude/sessions/.current-sessionfor the active session - •
If no active session, inform user there's nothing to end
- •
If session exists, append a comprehensive summary including:
- •Session duration
- •Git summary:
- •Total files changed (added/modified/deleted)
- •List all changed files with change type
- •Number of commits made (if any)
- •Final git status
- •Todo summary:
- •Total tasks completed/remaining
- •List all completed tasks
- •List any incomplete tasks with status
- •Key accomplishments
- •All features implemented
- •Problems encountered and solutions
- •Breaking changes or important findings
- •Dependencies added/removed
- •Configuration changes
- •Deployment steps taken
- •Lessons learned
- •What wasn't completed
- •Tips for future developers
- •
Empty the
.claude/sessions/.current-sessionfile (don't remove it, just clear its contents) - •
Inform user the session has been documented
The summary should be thorough enough that another developer (or AI) can understand everything that happened without reading the entire session.