save-memory
Manually save current session memory to files
When & Why to Use This Skill
The 'save-memory' Claude skill enables users to manually persist session context and progress into structured local files. It solves the problem of context loss in long-running tasks by creating immediate checkpoints that document summaries, decisions, patterns, and extracted facts, ensuring continuity and long-term knowledge retention across different AI interactions.
Use Cases
- Development Checkpointing: Manually save a snapshot of the current session progress before starting a major code refactor, allowing for a clear reference point of the previous state.
- Knowledge Base Integration: Exporting session-specific decisions and architectural patterns into a permanent 'memory.md' file to build a long-term project knowledge base.
- Complex Debugging Continuity: Saving the state of a deep-dive debugging session to ensure that identified facts and resolved issues are preserved if the session needs to be resumed later.
- Project Handoff and Documentation: Generating structured session files that can be shared with team members to provide a concise summary of accomplishments and technical decisions made during an AI pairing session.
| name | save-memory |
|---|---|
| description | Manually save current session memory to files |
Save Memory
Force immediate save of session memory.
Usage
/memory-keeper:save-memory
Actions
- Save to memory.md:
echo -e "\n## $(date +%Y-%m-%d_%H%M)\n[Summary of current session progress]" >> ".claude/memory/memory.md"
- Create session file:
cat > ".claude/memory/sessions/$(date +%Y-%m-%d_%H%M).md" << 'ENDSESSION'
# Session TIMESTAMP
## Summary
[What has been accomplished so far]
## Decisions
- [type] Decision: Reason
- files: affected files
- concepts: relevant concepts
## Patterns
- [type] Pattern observed
- concepts: tags
## Issues
- [type] Issue: open|resolved
- files: affected files
ENDSESSION
- Extract facts:
node "scripts/counter.js" extract-facts TIMESTAMP
Notes
- Uses same format as auto-save
- Does NOT reset counter (auto-save will still trigger normally)
- Use when you want to checkpoint progress mid-session