Where are my session notes stored?

All data is saved locally to your project directory within the .claude/memory/ folder in standardized markdown format.

Can I use this skill to restore a previous state?

While it saves information to files that Claude can read for context, it is primarily a documentation and memory persistence tool rather than a traditional git-style 'undo' command.

Does this skill replace the Claude Code auto-save feature?

No, it complements auto-save by allowing you to manually trigger a save at any time without resetting the internal auto-save counter.

What kind of data is captured in a manual save?

The skill captures a session summary, architectural decisions, observed patterns, and the status of open or resolved issues.

Session Memory Keeper

Name: Session Memory Keeper
Author: ZipperBagCoffee

byZipperBagCoffee

Productivity & Workflow

Enables manual checkpointing of session progress, architectural decisions, and coding patterns to persistent markdown files.

About

Session Memory Keeper is a specialized utility for Claude Code that allows developers to force an immediate save of their current session context. By capturing summaries, decisions, and patterns into the .claude/memory directory, it ensures that critical project knowledge is never lost between sessions. This skill is ideal for developers working on complex tasks who want to create manual checkpoints or document their reasoning mid-workflow without waiting for automatic triggers.

Key Features

Structured capture of architectural decisions and patterns
0 GitHub stars
Non-disruptive integration with existing auto-save counters
Force immediate session memory snapshots
Persistent markdown-based storage for easy auditing
Automated timestamping for session logs

Use Cases

Creating a permanent record of resolved issues before switching project context
Checkpointing progress during complex multi-file refactoring
Documenting specific architectural trade-offs immediately after they are made

About

Key Features

Structured capture of architectural decisions and patterns
0 GitHub stars
Non-disruptive integration with existing auto-save counters
Force immediate session memory snapshots
Persistent markdown-based storage for easy auditing
Automated timestamping for session logs

Use Cases

Creating a permanent record of resolved issues before switching project context
Checkpointing progress during complex multi-file refactoring
Documenting specific architectural trade-offs immediately after they are made