end-session

Capture session decisions and file changes into CLAUDE.md and CHANGELOG.md.

1|Updated Dec 13, 2025
One-click install
npx skills add https://github.com/SomtechSolutionMAxime/somtech-pack --skill end-session-somtechsolutionmaxime
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: end-session
Source: https://github.com/SomtechSolutionMAxime/somtech-pack/tree/main/.claude/skills/end-session
Command: npx skills add https://github.com/SomtechSolutionMAxime/somtech-pack --skill end-session-somtechsolutionmaxime

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically captures and organizes the outcomes of a Claude Code session, preserving decisions, actions, and file changes into project memory.

Core Features & Use Cases

  • Automatically extract decisions, issues resolved, and changes from the current session
  • Update CLAUDE.md with structured notes and a concise session summary
  • Append entries to CHANGELOG.md to document progress for future teams

Quick Start

Run the /end-session command to automatically document the current Claude Code session and update CLAUDE.md and CHANGELOG.md.

Frequently Asked Questions about end-session

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

FAQPage Schema
How do I automate session documentation for Claude Code?

You can automate session documentation by running the /end-session command, which extracts decisions, resolved issues, and changed files to generate a concise project memory and changelog entries automatically.

What is the best way to update CLAUDE.md and CHANGELOG.md after coding?

The best way to update CLAUDE.md and CHANGELOG.md is using automated session documentation that captures session outcomes, ensures non-duplication, and applies readable formatting to both project memory and changelog files.

Does session management automation work without external dependencies?

Yes, session management automation works without external dependencies, directly capturing decisions and file changes from the ongoing Claude Code session to append structured notes and changelog entries.

How does automated changelog generation prevent duplicate entries?

Automated changelog generation prevents duplicate entries by extracting session outcomes and applying non-duplication logic before appending structured, readable updates to CHANGELOG.md.

Why do I need to document Claude Code sessions for future reference?

You need to document Claude Code sessions to preserve decisions, actions, and file changes into a structured project memory, ensuring future teams can reference progress and resolved issues efficiently.