session_skill

Overview

This skill provides a unified gateway for managing Claude Code sessions, handling initialization, memory persistence, state control, and cross-session messaging. It centralizes session operations so you can start, resume, fork, inspect inboxes, and broadcast messages from a single command surface.

How this skill works

The skill inspects the current project context, loads or creates session state files, and persists learnings to persistent memory files. It exposes commands to list active sessions, check incoming messages, broadcast to sessions, and control resume/fork flows while optimizing memory usage during long-running workflows.

When to use it

• Initialize a new Claude Code session and load project context.
• Resume or fork a working session with --resume or --fork flags.
• Send announcements or coordination messages to all active sessions.
• Inspect incoming cross-session messages or event logs.
• Persist session learnings and prepare handoff summaries.

Best practices

• Use frequent --resume calls for long sessions to reduce memory usage and keep context focused.
• Split large refactors into feature-specific sessions to simplify state and handoffs.
• Run /session list to confirm active sessions before broadcasting messages.
• Store recurring notes and lessons in the persistent memory files for smooth resumption.
• Use automatic rename (no-arg /rename) to generate clear session names from context.

Example use cases

• Start a new feature development cycle: initialize session, implement, then persist memory and handoff.
• Resume a paused implementation after an hour using claude --resume to benefit from memory optimizations.
• Fork a session to experiment with an alternate approach without losing the original context.
• Broadcast a review-ready message to all active sessions before merging a change.
• Check the session inbox to see status updates from parallel tasks or collaborators.