README
Claude Code starts every session with a blank slate. The quirk you debugged yesterday, the plan you were halfway through — all gone when the session ends. ccmemo saves that knowledge and progress as Markdown files in your repository, so the next session picks up where you left off.
ccmemo adds four slash commands that persist knowledge and plans as plain Markdown in
.claude/:
| Command | What it does | More |
|---------|--------------|------|
| /record-knowledge | Save a quirk, pitfall, or decision as a tagged entry | Example |
| /recall-knowledge | Hybrid semantic search across entries (synonyms, cross-language) | docs/hybrid-search.md |
| /review-knowledge | Keep the knowledge base healthy — stale/orphan entries, missing links, tag issues | Reviewing |
| /plan-task | Persist multi-step plans and progress across sessions | Plan & task |
Claude Code invokes these automatically when relevant; you can also trigger any of them by name.
Up and running in three steps. The plugin is the recommended path — skills and hooks activate the moment it's installed.
1. Install the plugin (in Claude Code):
/plugin marketplace add LevNas/claudecode-plugins
/plugin install ccmemo@levnas-plugins
That alone makes /record-knowledge, /plan-task, /review-knowledge, and
/recall-knowledge available and wires up the Context Guard hooks.
2. Scaffold the starter config into your project — a tag registry for knowledge and an index for tasks. Easiest is to just ask Claude Code:
Sc