Our review

Properly closes a Claude Code session by updating memory files and optionally committing Git changes.

Strengths

Ensures continuity between sessions by preserving context in dedicated files.
Structures documentation of completed work and next steps.
Integrates Git commit management to prevent loss of work.

Limitations

Specifically designed for Claude Code, not compatible with other tools without adaptation.
Requires manual execution at the end of a session.
Can be verbose for very short sessions.

When to use it

Use at the end of each Claude Code work session to ensure smooth resumption.

When not to use it

Avoid for minor changes or exploratory sessions with no concrete results.

Examples

End session with commit

Sign off this session: update handoff notes and commit changes with a summary of what we did.

Quick handoff update

Close session and update PROJECT.md handoff with status and next steps.

Session wrap-up

End session: update session history, handoff, and HISTORY.md. Then show git status and offer to commit.

name: signoff description: End session - update session history, handoff note, and HISTORY.md if needed allowed-tools: Read, Write, Edit, Glob

Sign Off / End Session

Properly close out a Claude Code session by updating all memory files.

Instructions

Step 1: Gather Session Context

Read the current session file from .claude/memory/sessions/session-history-{DATE}.md
Read .claude/PROJECT.md to see current handoff state (or CLAUDE.md if no PROJECT.md exists)
Read .claude/memory/HISTORY.md to see format and recent entries
Review conversation to identify what was accomplished this session

Step 2: Update Session History File

Update today's session file (/app/.claude/memory/sessions/session-history-{DATE}.md) with:

Summary of work completed
Any issues encountered
Decisions made and rationale
Any incomplete work or next steps

Step 3: Update PROJECT.md Handoff

Update the "Current Session Handoff" section in .claude/PROJECT.md with:

Today's date
Brief status summary
What was done this session (bullet points)
Any running servers or temporary state to be aware of
Outstanding work / next steps

Step 4: Update HISTORY.md

One entry per day - HISTORY.md should have a single dated entry for each day, updated as sessions progress. Don't create separate entries per session.

Check if today's entry exists:

If yes: Update it with new accomplishments from this session
If no: Create a new dated entry

Include significant work:

Features completed or major progress
Bugs fixed
Architectural changes
New tools, skills, or documentation created

Skip only for truly minor sessions (typo fixes, failed exploration, no real progress).

Format: Summary sections with bullet points, status table if relevant, link to detailed session notes.

Step 5: Report to User

Provide a brief summary:

What was accomplished
What's documented where
Any next steps or outstanding items
Confirm they're ready to close the session

Step 6: Check and Commit Git Changes

Usually the project should have one root-level repository, but there may be multiple. For each repo with uncommitted changes:

Show the user what changed
Offer to commit with a brief message summarizing the session's work
Keep commit messages to one line when possible

Notes

Keep handoff notes concise but complete enough for a fresh Claude instance to pick up
Session history files can be more detailed - that's where the "how and why" lives
Always check both repos before signing off - uncommitted work can be lost between sessions
Follow git safety rules: no --amend, --force, or history rewriting inside the sandbox

Sign Off Session

Recommended for