analyze
CommandAnalyze user corrections and log them into the error notebook
Restore memory from your GitHub backup when local memory files are lost or corrupted. Also works for cross-device sync.
Restore memory from your GitHub backup when local memory files are lost or corrupted. Also works for cross-device sync.
You need a GitHub repo set up as your memory backup (the one you push to with `/backup` or `/sync`). If you haven't created a backup repo yet, this command won't work.
bash ~/.claude/scripts/hooks/memory-backup.sh pull
The `pull` mode does two things: 1. `git pull` from GitHub to get the latest 2. Distribute `repo/memory/*.md` into every local project directory that has a `memory/` folder (newer file wins, won't overwrite local changes)
This solves the "Device A pushed but Device B can't see it" problem -- each device has different working directories, so `projects/` paths differ. Global memory must be actively distributed.
1. **Protect current state** -- Run `/backup` first to push any remaining local changes 2. **Pull from GitHub** -- `bash ~/.claude/scripts/hooks/memory-backup.sh pull` 3. **Verify** -- Read MEMORY.md, scan all index entries 4. **Report** -- "Recovered! Found {N} index entries, {M} memory files"
Claude Code 的記憶系統 | A memory system built with hooks + markdown. Zero dependencies.
Analyze user corrections and log them into the error notebook
Pause the SessionEnd auto-commit hook when refactoring core engine files.
Help decide when to use `/compact` based on the current conversation state.
Review the error notebook — flip through past corrections before working
Implement tasks incrementally — build, test, verify, commit. Add "auto" to run the whole plan in one approved pass.