memory-save

Generate a dated session summary and update persistent context files.

Updated Feb 1, 2026

Search Tags:#session management #progress tracking #session summary #context saving #code continuity

Ready to run

npx skills add https://github.com/whjelmar/claude-memory-system --skill memory-save-whjelmar

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: memory-save
Source: https://github.com/whjelmar/claude-memory-system/tree/main/skills/memory-save
Command: npx skills add https://github.com/whjelmar/claude-memory-system --skill memory-save-whjelmar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the ephemeral nature of Claude Code sessions by providing a mechanism to save the current work, decisions, and context, ensuring continuity across sessions.

Core Features & Use Cases

Session Summarization: Automatically generates a summary of work completed, decisions made, discoveries, and open items.
Context Preservation: Updates a persistent context file to help the next session pick up exactly where the last one left off.
Progress Tracking: Integrates with project plans to mark off completed tasks.
Use Case: At the end of a coding session, use this skill to save your progress, document key decisions, and ensure the next session starts with all necessary information to continue efficiently.

Quick Start

Use the memory save skill to save your current session progress and context.

Frequently Asked Questions about memory-save

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

FAQPage Schema

How do I save my Claude Code session context before closing it?▼

Session summarization works by gathering your input on completed work, decisions, and discoveries, then generating a dated summary file and updating a persistent context file to preserve project continuity.

How do I track project progress across multiple coding sessions?▼

You can track project progress across coding sessions by updating a persistent context file and marking off completed tasks if an active project plan exists, ensuring the next session resumes efficiently.

What's the best way to preserve code continuity when ending a development session?▼

The best way to preserve code continuity is documenting key decisions and open items in a dated summary file, which feeds a persistent context file so the next session picks up exactly where you left off.

Does this session management approach require an active project plan to work?▼

No, an active project plan is not required. The skill saves your session context and generates a summary file regardless, but it will additionally update project progress tracking if a plan exists.

Can I use context saving to document decisions and discoveries made during coding?▼

Yes, context saving explicitly documents decisions and discoveries made during coding. You provide these details, and the skill records them in a summary file for future reference and session handoffs.