end
This skill contains shell command directives (!`command`) that may execute system commands. Review carefully before installing.
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.
More from cadrianmae/claude-marketplace
datetime
Use the `date` command via Bash tool whenever you or the user mention time, dates, or temporal concepts. Verify current date/time before ANY temporal response, as environment context may be outdated. Parse expressions like "tomorrow", "next week", "3 days", "in 2 weeks", "next Monday at 3pm". Proactively invoke for deadlines, schedules, time-sensitive tasks, week numbers, or any date/time reference.
70pandoc
Automatically assist with Pandoc document conversions when user mentions converting markdown to PDF/DOCX/HTML or other formats. Validate YAML frontmatter, check dependencies (bibliography, images), and provide format-specific conversion guidance. Use when user asks about citations, academic papers, presentations, or document generation from markdown.
6update
Update the current development session with progress notes
5list
List all development sessions
5nvr-list
This skill should be used when the user asks to "list neovim instances", "show all nvim", "what neovim processes are running", "list all editors", "show all active neovim", or wants to see all running neovim instances across all projects.
5current
Show the current session status
5