Slash Command91 repo starsupdated 9d ago

save

The save command persists context information to a branch-aware memory bank located at the repository root under `.claude/memory-bank/`. Use this command to record session notes, decisions, and work progress organized by git branch and date, enabling context retention across multiple Claude Code sessions and team collaboration when the memory bank is committed to version control.

View source Repository: claude-code-riper-5

Install in Claude Code

Copy

mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/tony/claude-code-riper-5/HEAD/.claude/commands/memory/save.md -o ~/.claude/commands/save.md

Then start a new Claude Code session; the slash command loads automatically.

Definition

save.md

# Saving to Memory Bank

## ⚠️ Memory Bank Location Requirements

**CRITICAL PATH POLICY**: 
- Memory-bank MUST be at repository root: Use `git rev-parse --show-toplevel` to find root, then `[ROOT]/.claude/memory-bank/`
- NEVER create package-level memory-banks: `packages/*/.claude/memory-bank/` ❌
- In monorepos: ONE memory-bank at root serves entire project

### Correct vs Incorrect Paths
✅ **Correct**: `[ROOT]/.claude/memory-bank/main/session.md` (where ROOT = `git rev-parse --show-toplevel`)
❌ **Wrong**: `[ROOT]/packages/react/.claude/memory-bank/main/session.md`
❌ **Wrong**: `packages/react/.claude/memory-bank/main/session.md`

I'll save the following information to the branch-aware memory bank:

## Context Information
- **Date**: !`date +%Y-%m-%d`
- **Time**: !`date +%H:%M:%S`
- **Branch**: !`git branch --show-current`
- **Latest Commit**: !`git log -1 --oneline`
- **Working Directory Status**: !`git status --short`

## Memory Content
$ARGUMENTS

## Storage Location
The memory will be saved to:
1. First run: `git rev-parse --show-toplevel` to get repository root
2. Save to: `[ROOT]/.claude/memory-bank/!`git branch --show-current`/!`date +%Y%m%d`-session.md`

This ensures memories are:
- Branch-specific (won't conflict when switching branches)
- Date-organized (easy to find recent work)
- Persistent across sessions
- Shareable with team (can be committed if desired)