workspace-memorylisted

Use this skill as the project's long-term record, shared by Claude Code, Gemini CLI and Codex across sessions. You don't remember past sessions yourself, so use it whenever a message depends on or changes what was discussed before, even if the word 'memory' never comes up: (1) recall: 'what did we decide/agree', 'why did we drop X', 'catch me up', 'where did we leave off', any mention of yesterday, last week or earlier meetings; (2) updates worth keeping: decisions, corrections ('actually it moved to…'), blockers or waiting-on items, deadlines, status changes, preferences, 'keep track of / don't let me forget'; (3) upkeep: a 'Memory review due' prompt, or a request to review, tidy or prune what's remembered; (4) setup: making several sessions or AI tools share context for a project or planning workspace, or linking code repos to it. Don't use it for RAM or memory-leak problems, Jira tickets, one-off meeting summaries, importing another assistant's memories, or Claude's built-in /memory.
rajbdilip/skills · ★ 1 · AI & Automation · score 77

Install: claude install-skill rajbdilip/skills

# Workspace Memory Memory lives in `memory/` inside a workspace and is committed to Git. Scripts in this skill do all file editing, because they validate input, file each item in the right place, remove duplicates and keep links and indexes consistent; hand edits drift. Your job is to decide **what** is worth remembering and pass it to one command. Commands below assume the skill is at `~/.claude/skills/workspace-memory`. If the session context shows a different path for `capture.mjs`, use that path instead. ## 1. Setup (only when asked, or when no `.workspace-memory/config.json` exists) | Situation | Run | | --- | --- | | Hooks not installed on this machine yet | `node ~/.claude/skills/workspace-memory/scripts/install.mjs --scope global` | | New planning or non-coding workspace | `node ~/.claude/skills/workspace-memory/scripts/init.mjs --target <dir>` | | Link a code repo to a planning hub | `node ~/.claude/skills/workspace-memory/scripts/init.mjs --target <hub> --link <repo> --name <short-name>` | Add `--dry-run` to preview any of these. ## 2. At session start If the session context already contains "Workspace memory is active", the files are loaded. Do not read them again. Otherwise read `memory/PROFILE.md`, `memory/CURRENT.md`, `memory/ACTIVE_THREADS.md` and `memory/INDEX.md`. Open other memory files only when the task needs them. To find older context, search. Do not open files one by one: ```bash node ~/.claude/skills/workspace-memory/scripts/search.mjs "caterer