Session Management
Name, checkpoint, and resume Claude Code sessions so long debugging or feature work survives pauses and context switches.
Overview
Session Management is a journey-wide agent skill that names, checkpoints, and resumes Claude Code sessions—usable whenever a solo builder needs to preserve long agent context before pausing or switching machines.
Install
npx skills add https://github.com/athola/claude-night-market --skill session-managementWhat is this skill?
- Documents /rename, /resume, and claude --resume for named sessions (2.1.41+ auto-name on /rename)
- Debugging pattern: /rename debugging-auth-issue then claude --resume debugging-auth-issue
- Feature checkpoint pattern: milestone-based /rename then continue or resume later
- Explicit When NOT To Use: skip for short sessions and fresh starts with no prior context
- 3 documented commands (/rename, /resume, claude --resume)
- 2 workflow patterns (debugging sessions, feature checkpoints)
Adoption & trust: 1 installs on skills.sh; 304 GitHub stars; 2/3 security scanners passed (skills.sh audits); trending (+100% hot-view momentum).
What problem does it solve?
You lose hours of agent context when a Claude Code session ends and you have no named checkpoint to resume the same debugging or feature thread.
Who is it for?
Multi-session debugging, long feature builds, and any Claude Code work where you expect to stop and return with the same session identity.
Skip if: One-shot tasks finished in a single short chat or brand-new work with zero prior session state to restore.
When should I use this skill?
Managing session checkpoints and state preservation or resuming work across Claude Code sessions.
What do I get? / Deliverables
You run /rename at milestones, auto-save on pause, and resume with /resume or claude --resume <name> so work continues without re-briefing the agent.
- Named session identity
- Resumable checkpoint for continued agent work
Recommended Skills
Journey fit
Useful at every journey phase - explore requirements and options before committing to a direction.
Where it fits
Rename to feature-x-milestone-1 after the first slice ships in agent, then resume tomorrow without re-explaining the spec.
Keep debugging-auth-issue as the session name while chasing API errors across several Claude Code windows.
Pause mid-test-harness fix and resume the same named session when CI fails again overnight.
Resume production incident investigation with claude --resume after switching from laptop to desktop.
How it compares
Use instead of leaving default unnamed sessions and manually pasting old chat logs back into a new thread.
Common Questions / FAQ
Who is session-management for?
Solo and indie builders who live in Claude Code for multi-hour debugging, features, or ops fixes and need durable session handles across days.
When should I use session-management?
During build when iterating a feature across sessions, during ship when debugging flaky tests over multiple runs, and during operate when resuming an incident thread—anytime long-running agent work needs a named checkpoint.
Is session-management safe to install?
It is procedural documentation for Claude Code commands with no shell or network side effects; review the Security Audits panel on this Prism page before trusting any third-party skill package.
SKILL.md
READMESKILL.md - Session Management
# Session Management ## When To Use - Managing session checkpoints and state preservation - Resuming work across Claude Code sessions ## When NOT To Use - Short sessions that do not need checkpoints - Fresh starts where no prior session context exists ## Overview Claude Code supports named sessions for better workflow organization. Use this skill to manage complex, long-running work across multiple sessions. ## Available Commands | Command | Description | |---------|-------------| | `/rename` | Name the current session (auto-generates name if no argument given, 2.1.41+) | | `/resume` | Resume a previous session (REPL) | | `claude --resume <name>` | Resume from terminal | ## Workflow Patterns ### 1. Debugging Sessions Name debug sessions for easy resumption: ``` # Start debugging /rename debugging-auth-issue # ... work on the issue ... # If you need to pause, session is auto-saved # Resume later: claude --resume debugging-auth-issue ``` ### 2. Feature Development Checkpoints Create checkpoints during long feature work: ``` # After completing milestone 1 /rename feature-x-milestone-1 # Continue in new session # Reference old session if needed ``` ### 3. PR Review Sessions For complex PR reviews that span multiple sittings: ``` # Start review /rename pr-review-123 # Take breaks without losing context # Resume: claude --resume pr-review-123 ``` ### 4. PR-Linked Sessions (Claude Code 2.1.27+) Sessions are automatically linked to PRs when created via `gh pr create`. Resume PR-specific sessions later: ``` # Resume session for a specific PR claude --from-pr 156 claude --from-pr https://github.com/org/repo/pull/156 # Workflow: review → pause → resume with full context /rename pr-review-156 # ... review work ... # Later: claude --from-pr 156 ``` ### 5. Investigation Sessions When investigating issues that may require research: ``` # Start investigation /rename investigate-memory-leak # Pause to gather more info externally # Resume with full context: claude --resume investigate-memory-leak ``` ## Resume Screen Features The `/resume` screen provides: - **Grouped forked sessions**: See related sessions together - **Keyboard shortcuts** (defaults, customizable via `/keybindings`): - Preview session content - Rename a session - **Recent sessions**: Sorted by last activity ### 6. Resume Hint on Exit (Claude Code 2.1.31+) Claude Code now shows a resume hint when you exit, displaying the command to continue your conversation. This makes session resumption more discoverable: users no longer need to know about `--resume` beforehand. ## Best Practices ### Naming Conventions Use descriptive, hyphenated names: | Pattern | Example | Use Case | |---------|---------|----------| | `debugging-<issue>` | `debugging-auth-401` | Bug investigation | | `feature-<name>-<milestone>` | `feature-search-v2` | Feature development | | `pr-review-<number>` | `pr-review-156` | PR reviews | | `investigate-<topic>` | `investigate-perf` | Research | | `refactor-<area>` | `refactor-api-layer` | Refactoring work | ### When to Name Sessions Name sessions when: - Work will span multiple days - You might need to pause unexpectedly - The session contains valuable context - You want to reference it later ### Session Cleanup Unnamed sessions are eventually garbage collected. Named sessions persist longer. Periodically clean up old named sessions you no longer need. ## Integration with Sanctum Combine session management with other Sanctum skills: 1. **Before starting**: Run `Skill(sanctum:git-workspace-review)` to capture context 2. **Name the session**: `/rename <descriptive-name>` 3. **Wo