memory-autosave

name	memory-autosave
description	Auto-executes when the [CRABSHELL_SAVE] trigger is detected in hook output. Saves session memory following a numbered step sequence. Not user-invocable — triggered automatically by the plugin system.

Node.js Path

Use the Node.js absolute path from your context's "Node.js Path" section (injected by the plugin on every prompt). If not available in context, fall back to node.

Script Path Resolution

IMPORTANT: The scripts/ folder is in the plugin directory, NOT the current project.

From "Base directory for this skill:" above, derive the scripts path:

• Remove /skills/memory-autosave from the end
• Add /scripts/ to get the scripts directory

Example: if Base directory is ~/.claude/plugins/cache/.../skills/memory-autosave, then Scripts path is derived by removing /skills/memory-autosave and appending /scripts/.

Use this full path when running node commands below.

Project Root Resolution

IMPORTANT: Get the project root from your context's "Project Root Anchor" section. Look for: Your ACTUAL project root is: <path>

Use this value as {PROJECT_DIR} in all commands below. If not available in context, use your current working directory.

Memory Save Skill

This skill activates when [CRABSHELL_SAVE] appears in conversation.

Memory Structure

.crabshell/memory/
  project.md        <- Project overview (per-prompt injected)
  logbook.md        <- Rolling session log (last 50 lines loaded)
  sessions/         <- L1 session transcripts (auto-generated)
  logs/             <- Debug and error logs

Trigger Message

═══════════════════════════════════════════════════════════════
[CRABSHELL_SAVE] AUTO-SAVE TRIGGERED - N tool uses reached
═══════════════════════════════════════════════════════════════

Required Actions

Step 1: Save to logbook.md

Generate a timestamp, then write the summary to a temp file and use append-memory.js:

1. Use the Write tool to save a 1-2 sentence session summary to {PROJECT_DIR}/.crabshell/memory/delta_summary_temp.txt
2. Run:

"{NODE_PATH}" "{SCRIPTS_PATH}/append-memory.js" --project-dir="{PROJECT_DIR}"

If append-memory.js is not available, use the timestamp + Edit tool approach:

"{NODE_PATH}" -e "const fs=require('fs');const d=new Date();const p=n=>String(n).padStart(2,'0');const ts=d.getFullYear()+'-'+p(d.getMonth()+1)+'-'+p(d.getDate())+'_'+p(d.getHours())+p(d.getMinutes());fs.appendFileSync('{PROJECT_DIR}/.crabshell/memory/logbook.md','\\n## '+ts+'\\n')"

Then use the Read tool to read {PROJECT_DIR}/.crabshell/memory/logbook.md, and use the Edit tool to append the 1-2 sentence summary after the timestamp heading.

Session End (Stop Hook)

Additional step (use full path from above):

"{NODE_PATH}" "{SCRIPTS_PATH}/counter.js" compress --project-dir="{PROJECT_DIR}"

Optional: Update Hierarchical Memory

If major project understanding changed, update stable memory files (use full path):

"{NODE_PATH}" "{SCRIPTS_PATH}/counter.js" memory-set project "Updated project description..." --project-dir="{PROJECT_DIR}"

When to update:

• project.md: New project scope, goals, or tech stack

View current memory:

"{NODE_PATH}" "{SCRIPTS_PATH}/counter.js" memory-list --project-dir="{PROJECT_DIR}"
"{NODE_PATH}" "{SCRIPTS_PATH}/counter.js" memory-get project --project-dir="{PROJECT_DIR}"

Critical

• DO NOT SKIP the logbook.md append step
• Counter resets automatically (no manual reset needed)

See Architecture for full details.