From recall
Save a mid-session recall checkpoint — captures what happened so far to episodic memory without ending the session. Use when the user says 'save recall', 'checkpoint', 'save memory', 'save session state', or before restarting/exiting a long session. Also use when the user worries about losing context in a long-running session.
How this skill is triggered — by the user, by Claude, or both
Slash command
/recall:saveThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are saving a mid-session checkpoint to recall's episodic memory. Since you (Claude) have full context of this session, you write the episodic entry directly — no haiku call needed.
You are saving a mid-session checkpoint to recall's episodic memory. Since you (Claude) have full context of this session, you write the episodic entry directly — no haiku call needed.
PROJECT_HASH=$(printf '%s' "$(pwd)" | shasum -a 256 | cut -c1-12)
RECALL_DIR="${CLAUDE_PLUGIN_DATA:-${HOME}/.recall}/projects/${PROJECT_HASH}"
mkdir -p "${RECALL_DIR}/episodic"
git log --oneline --since='12 hours ago' --no-merges | head -10
### HH:MM — <one-line summary of session so far>
- **Goal:** <what the user wanted>
- **Outcome:** <what has been achieved so far>
- **Key files:** <comma-separated list of files changed>
- **Decisions:** <notable choices made, or 'None'>
- **Open:** <work still in progress>
- **Note:** Mid-session checkpoint (session still active)
Use the actual current time for HH:MM. Be specific — use real file names, real decisions, real outcomes. The git log is your ground truth for what was committed.
TODAY=$(date +%Y-%m-%d)
EPISODIC_FILE="${RECALL_DIR}/episodic/${TODAY}.md"
# Create header if file doesn't exist
if [ ! -f "$EPISODIC_FILE" ]; then
printf '# %s\n\n' "$TODAY" > "$EPISODIC_FILE"
fi
# Append the entry (use cat <<'ENTRY' heredoc)
cat <<'ENTRY' >> "$EPISODIC_FILE"
<your structured entry here>
ENTRY
npx claudepluginhub flight505/recallSaves current work session to persistent memory by summarizing accomplishments, tracking modified files, and storing learnings for cross-session continuity. Invoke via /remember after activity.
Saves session state and writes a handoff note so the next Claude Code session can continue cleanly. Read/writes a remember.md file at the project root.
Generates and saves Markdown session logs capturing objectives, file changes, referenced materials, technical notes, future plans, open items, and metrics to resume project work across conversations.