Save an unfinished session as a timestamped Markdown handoff. Capture changed files, decisions and their reasons, current progress, blockers, and ordered next steps so work can resume later or continue in another Claude instance.
Save the current session state (decisions, modified files, current status, and next steps) to a handoff file for later resume.
Review the instructions the agent will receive before you install.
Capture the current session into a structured handoff file so you (or another instance) can resume with full context. Creates a timestamped Markdown file in .claude/sessions/.
Produce a handoff document with the following structure:
[One paragraph: the goal, the approach, where things stand right now]
[List every file that was created, edited, or deleted, with the nature of the change]
path/to/file.ts - [what changed and why]
path/to/other.ts - [what changed and why]
[Architectural choices, tradeoffs accepted, approaches rejected and why]
[Where things are right now: what's working, what's broken, what's in-progress]
[The exact next actions to take to continue, specific enough that a fresh context can pick up without re-reading everything]
path/to/file.ts - [what to do][Files that must be read to resume with full understanding, keep this list short]
path/to/key-file.ts: [why it matters]CLAUDE.md: project rules[Anything unresolved that needs a decision or external input before proceeding]
Save the handoff to .claude/sessions/handoff-[YYYY-MM-DD-HHMM].md. Then output the file path so the user knows where to find it.
To resume from a handoff:
/session-resume .claude/sessions/handoff-YYYY-MM-DD-HHMM.md
Or manually: read the handoff file, then read the files listed in "Context to Reload" before continuing.
/session-save
Claude captures:
src/middleware/auth.ts, src/middleware/jwt.ts)refreshToken() in src/services/auth.service.ts, then update testsWhen context hits 70%, run /session-save before /compact to preserve decision context that compaction might lose.
See also:
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Evaluate Claude Code agents, skills, and commands with weighted quality criteria. Get scores, readiness grades, template comparisons, and practical improvement suggestions in Markdown or JSON reports to guide reviews before release.
Assess a codebase across seven areas, including exposed credentials, security, dependencies, structure, and tests. Receive category scores, findings tied to file locations, and a prioritized improvement plan with smaller tasks that can be completed quickly.
Measure code patterns such as casts to any or disabled lint rules, then run repeated, targeted edits. Keep changes that improve the chosen metric, revert unsuccessful changes, and track results for each improvement loop.
Generate several separate solutions, compare them against criteria fixed in advance, and verify the selected result through executable checks or an independent reviewer. Keep a proof log documenting candidates, evidence, failures, and remaining limits.
Monitor a live application after deployment and compare it with a saved baseline, a record of its earlier state. Check page responses, loading times, and new errors, flag persistent changes, and produce a per-page health report.
Rebuild project context after clearing a conversation or returning to work. Review recent Git history, uncommitted changes, and TODO markers to get a structured summary of project status and suggested next steps.