/session-start
I'll begin a documented coding session using Claude Code CLI's memory system.
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-start
Context preview
What this command does when you run it.
I'll begin a documented coding session using Claude Code CLI's memory system.
Command definition
session-start.mdStart Coding Session
I'll begin a documented coding session using Claude Code CLI's memory system.
I'll integrate with the native memory system by updating CLAUDE.md:
- Session timestamp and context
- Current git state and branch
- Session goals and objectives
- Progress tracking throughout our work
Let me check for existing memory files and update them appropriately:
- Project memory (./CLAUDE.md) for team-shared context
- User memory (~/.claude/CLAUDE.md) for personal session tracking
Please tell me: 1. What are we working on today? 2. What specific goals do you want to accomplish? 3. Any context I should know about?
I'll add this session context to your memory system using the `/memory` command functionality, ensuring our progress is tracked and can be resumed later. This integrates seamlessly with Claude Code CLI's native memory management rather than creating a separate system.
**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
The session context will be preserved in the appropriate CLAUDE.md file for future reference and continuation.
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

