memory-save

Preserve session context and generate a structured handoff prompt for new sessions.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/leessju/claude-skills --skill memory-save-leessju
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memory-save
Source: https://github.com/leessju/claude-skills/tree/main/memory-save
Command: npx skills add https://github.com/leessju/claude-skills --skill memory-save-leessju

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Save current session context and generate a handoff prompt for continuing in a new session. Use when the user says "memory-save", "세션 저장", "정리해줘", "context 저장", or when context usage is high and work needs to be preserved before compact or /clear. Also supports incremental saving during work.

Core Features & Use Cases

  • Incremental Save: automatically preserves progress when context is nearing limits to prevent context loss.
  • Full Save & Handoff: creates a persistent session record and a structured handoff prompt for seamless continuation.
  • Project Root & State Tracking: detects project root and maintains a dedicated .omc directory for sessions and summaries.
  • Handoff Consistency: updates a project summary and provides a ready-to-use prompt for starting the next session.

Quick Start

Instruct memory-save to store the current session context and generate a handoff prompt for a new session.

Frequently Asked Questions about memory-save

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

FAQPage Schema
How do I save session context before clearing or compacting a long-running workflow?

To prevent context loss in long-running workflows, an automatic incremental save feature preserves progress when context limits are nearing. This ensures that current work is automatically backed up before a session boundary is crossed or a context limit is reached.

What is the best way to hand off a high-context project to a new session?

The best way to hand off a high-context project is to generate a structured handoff prompt and persistent project summary. This captured state can be directly reused as a ready-to-use prompt to start the next session, ensuring seamless continuation across session boundaries.

Does memory-save require a specific project directory structure to store session records?

It requires identifying a project root, which is automatically detected during the save process. Once detected, it creates and maintains a dedicated .omc directory within the project to store all persistent session records and updated project summaries.

When should I use incremental saves versus a full session save and handoff?

Use incremental saves during active work when context usage is high to prevent data loss, while a full save and handoff is ideal when crossing session boundaries or reaching project milestones. A full save creates a persistent record and a ready-to-use prompt for starting the next session.