skills.rest
Tschonsen
TschonsenCOMMUNITY
Explore all skills by this author →
GitHub

session-end

Update CURRENT_STATE and append SESSION_HISTORY entries at session end.

Updated Apr 19, 2026
Search Tags:#workflow#claude#state-management#session-history#session-end#project-maintenance#brain-files
One-click install
npx skills add https://github.com/Tschonsen/spec-driven-claude-development --skill session-end-tschonsen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: session-end
Source: https://github.com/Tschonsen/spec-driven-claude-development/tree/main/plugin/sdcd/skills/session-end
Command: npx skills add https://github.com/Tschonsen/spec-driven-claude-development --skill session-end-tschonsen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Close Claude sessions cleanly by updating CURRENT_STATE and appending a SESSION_HISTORY entry when needed, ensuring brain files stay fresh for the next session.

Core Features & Use Cases

  • Automates end-of-session wrap-up: updates state, ensures brain files are refreshed, and preserves session history when configured.
  • Supports mid-session rollover: allows a safe handoff by persisting latest changes before a context switch.
  • Use Case: As you finish coding, invoke this skill to lock in progress and prepare a clean start for the next session.

Quick Start

Tell Claude to run the session-end workflow to close the current session and refresh the project state.

Frequently Asked Questions about session-end

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I save Claude session state before closing a project?▼

To save Claude session state before closing a project, run the session-end workflow to update CURRENT_STATE.md and append SESSION_HISTORY.md. This persists your progress and ensures brain files stay fresh for the next session.

What is the best way to persist project state during a Claude context rollover?▼

The best way to persist project state during a Claude context rollover is invoking the session-end workflow. It safely hands off your latest changes by updating brain files and current state before you switch contexts.

Does the session-end workflow automatically commit my files to version control?▼

No, the session-end workflow does not automatically commit your files to version control. It includes specific safeguards to avoid auto-commit, ensuring your version control history remains manually managed.

Do I need a SESSION_HISTORY.md file to refresh my Claude project state?▼

No, you do not need a SESSION_HISTORY.md file to refresh your Claude project state. The workflow appends session history when the file is present, but only access to design/CURRENT_STATE.md is required.

How does session history append prevent unbounded state file growth?▼

Session history append prevents unbounded state file growth through built-in safeguards within the workflow. It updates the current state and manages SESSION_HISTORY.md entries to keep the next session starting state accurate without bloating files.

Related Skills

Explore More Software Engineering Skills→
jasonmichaelbell78-creatorjasonmichaelbell78-creator

checkpoint

Save session state to .claude/state with optional MCP memory.

Community
Intermediate
Sh3rd3nSh3rd3n
3

pause

Save session context and stash modified files for future Claude Code sessions.

Community
Intermediate
mcampbellrmcampbellr

gsd-resume-work

Load project state, detect checkpoints, and present the next action.

Community
Advanced
ruskibeatsruskibeats

replay-state-from-session-branch

Merge the latest state snapshot from pi session history into persisted files.

Community
Intermediate