/session-end
I'll summarize this coding session and update the memory system with our accomplishments.
How it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/session-end
Context preview
What this command does when you run it.
I'll summarize this coding session and update the memory system with our accomplishments.
Command definition
session-end.mdEnd Coding Session
I'll summarize this coding session and update the memory system with our accomplishments.
Let me analyze what we accomplished by: 1. Reviewing files created/modified during our session 2. Checking git changes and commit history 3. Summarizing completed work and pending items
I'll update the appropriate CLAUDE.md file with:
- Session summary and accomplishments
- Files modified and their purposes
- Decisions made and rationale
- Pending work and next steps
- Any important context for future sessions
Session Summary:
Accomplished:
- All completed tasks from our conversation
- Files created/modified with their purposes
- Problems solved and solutions implemented
Pending Items:
- Tasks started but not completed
- Known issues requiring attention
- Recommended next steps
Handoff Notes:
- Key architectural decisions made
- Important context for team members
- Blockers or dependencies identified
- Technical debt considerations
**Important**: I will NEVER:
- Add "Co-authored-by" or any Claude signatures
- Include "Generated with Claude Code" or similar messages
- Modify git config or user credentials
- Add any AI/assistant attribution to the commit
- Use emojis in commits, PRs, or git-related content
I'll preserve this summary in your memory system, ensuring continuity for future sessions and seamless handoffs to team members. This integrates with Claude Code CLI's native memory management for persistent context.
Read more
End Coding Session
I'll summarize this coding session and update the memory system with our accomplishments.
Let me analyze what we accomplished by: 1. Reviewing files created/modified during our session 2. Checking git changes and commit history 3. Summarizing completed work and pending items
I'll update the appropriate CLAUDE.md file with:
- Session summary and accomplishments
- Files modified and their purposes
- Decisions made and rationale
- Pending work and next steps
- Any important context for future sessions
Session Summary:
Accomplished:
- All completed tasks from our conversation
- Files created/modified with their purposes
- Problems solved and solutions implemented
Pending Items:
- Tasks started but not completed
- Known issues requiring attention
- Recommended next steps
Handoff Notes:
- Key architectural decisions made
- Important context for team members
- Blockers or dependencies identified
- Technical debt considerations
**Important**: I will NEVER:
- Add "Co-authored-by" or any Claude signatures
- Include "Generated with Claude Code" or similar messages
- Modify git config or user credentials
- Add any AI/assistant attribution to the commit
- Use emojis in commits, PRs, or git-related content
I'll preserve this summary in your memory system, ensuring continuity for future sessions and seamless handoffs to team members. This integrates with Claude Code CLI's native memory management for persistent context.
Best Claude Code framework that actually save time. Built by a dev tired of typing "please act like a senior engineer" in every conversation.
Repo: notlikeDev/CCPlugins
Other commands on ccplugins.
- /cleanproject
I'll help clean up development artifacts while preserving your working code.
Open command - /commit
I'll analyze your changes and create a meaningful commit message.
Open command - /create-todos
I'll analyze recent operations and create contextual TODO comments in your code.
Open command - /docs
I'll intelligently manage your project documentation by analyzing what actually happened and updating ALL relevant docs accordingly.
Open command - /explain-like-senior
I'll explain this code as a senior developer would, focusing on the why behind decisions.
Open command - /find-todos
I'll locate all TODO comments and unfinished work markers in your codebase.
Open command

