end-session

Save session context and update checkpoints during session closure.

3|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/alxyrgin/agent-forge --skill end-session-alxyrgin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: end-session
Source: https://github.com/alxyrgin/agent-forge/tree/main/.claude/skills/end-session
Command: npx skills add https://github.com/alxyrgin/agent-forge --skill end-session-alxyrgin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures a clean and auditable termination of a working session by saving context, updating checkpoints, and preparing logs for future restoration.

Core Features & Use Cases

  • Saves session context to memory and checkpoints
  • Updates active-context and progress, creates a session log
  • Suitable for long-running tasks and collaborative sessions

Quick Start

Terminate an active session and trigger all cleanup steps with a single command.

Frequently Asked Questions about end-session

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

FAQPage Schema
How do I save session context and create a checkpoint before ending a development session?▼

To save session context and create a checkpoint, end-session captures the current context state, updates active-context and progress tracking, and writes a durable session log for future restoration.

What is the best way to ensure memory persistence and session auditing during closure?▼

Memory persistence and session auditing are enforced during closure by coordinating checkpoint updates, saving context restoration status, and logging participant attribution across dev-infra memory and task systems.

How does context restoration work after cleanly terminating a long-running task?▼

Context restoration after terminating a long-running task relies on the durable session log created during closure, which records the saved context, checkpoint updates, and progress tracking needed to resume work.

Can I use end-session for collaborative sessions and still track participant attribution?▼

Yes, end-session is suitable for collaborative sessions and explicitly enforces participant attribution during closure, ensuring individual contributions are logged alongside the saved context and checkpoint updates.

Does end-session require any dependencies to coordinate checkpoint updates across memory systems?▼

No, end-session has no external dependencies and independently coordinates checkpoint updates, context restoration status, and progress tracking across the dev-infra memory and task systems during session closure.

Why do I need to update active-context and progress when closing a session cleanly?▼

Updating active-context and progress when closing a session cleanly ensures the dev-infra memory and task systems retain an accurate, durable record of the current state for future restoration and auditing.