recall-forget
Mark memory entries as superseded. Preserves history, does not delete.
@davegoldblattInstall SkillDevelopment
Skill
/recall-context
Show what memory files are loaded and available in the current session.
Claude Code
$ npx -y skills add davegoldblatt/total-recall --skill recall-context --agent claude-code
Codex
$ npx skills add davegoldblatt/total-recall --skill recall-context -a codex -y
Cursor
$ npx skills add davegoldblatt/total-recall --skill recall-context -a cursor -y
Gemini CLI
$ npx skills add davegoldblatt/total-recall --skill recall-context -a gemini-cli -y
GitHub Copilot
$ npx skills add davegoldblatt/total-recall --skill recall-context -a github-copilot -y
OpenCode
$ npx skills add davegoldblatt/total-recall --skill recall-context -a opencode -y
Windsurf
$ npx skills add davegoldblatt/total-recall --skill recall-context -a windsurf -y
SKILL.md
recall-context.SKILL.mddescription: Show what memory files are loaded and available in the current session.
Show what memory context is currently available in this session.
What To Do
1. Check What's Auto-Loaded
These files load automatically via Claude Code's native mechanisms:
**Via .claude/rules/ (deterministic):**
- .claude/rules/total-recall.md — memory protocol
**Via CLAUDE.local.md (deterministic):**
- CLAUDE.local.md — working memory
2. Check What Exists On Disk
Read and report on what memory files are present:
**Schema:**
- memory/SCHEMA.md — exists?
**Daily Logs:**
- Today's log (memory/daily/[today].md) — exists? Entry count?
- Yesterday's log — exists?
**Registers:**
- List all .md files in memory/registers/ with entry counts
**Archive:**
- List files in memory/archive/
3. Display
Memory Context — Current Session
─────────────────────────────────
Auto-loaded (deterministic):
.claude/rules/total-recall.md ✓ Protocol rules
CLAUDE.local.md ✓ Working memory ([N] words)
On disk:
memory/SCHEMA.md ✓ Protocol docs
memory/daily/[today].md ✓ [N] entries
memory/daily/[yesterday].md ✓ [N] entries
memory/registers/open-loops.md ✓ [N] active items
Available registers:
people.md [N] entries
projects.md [N] entries
decisions.md [N] entries
preferences.md [N] entries
tech-stack.md [N] entries
Archive: [N] files
Hooks:
SessionStart [configured/not configured]
PreCompact [configured/not configured]
4. Highlight Gaps
If expected files are missing:
Missing:
✗ CLAUDE.local.md — run /recall-init to create
✗ No daily log for today — will be created on first /recall-write
5. Quick Actions
Use /recall-search <query> to pull context from any tier.
Use /recall-status for memory health metrics.
Read more
description: Show what memory files are loaded and available in the current session.
Show what memory context is currently available in this session.
What To Do
1. Check What's Auto-Loaded
These files load automatically via Claude Code's native mechanisms:
**Via .claude/rules/ (deterministic):**
- .claude/rules/total-recall.md — memory protocol
**Via CLAUDE.local.md (deterministic):**
- CLAUDE.local.md — working memory
2. Check What Exists On Disk
Read and report on what memory files are present:
**Schema:**
- memory/SCHEMA.md — exists?
**Daily Logs:**
- Today's log (memory/daily/[today].md) — exists? Entry count?
- Yesterday's log — exists?
**Registers:**
- List all .md files in memory/registers/ with entry counts
**Archive:**
- List files in memory/archive/
3. Display
Memory Context — Current Session ───────────────────────────────── Auto-loaded (deterministic): .claude/rules/total-recall.md ✓ Protocol rules CLAUDE.local.md ✓ Working memory ([N] words) On disk: memory/SCHEMA.md ✓ Protocol docs memory/daily/[today].md ✓ [N] entries memory/daily/[yesterday].md ✓ [N] entries memory/registers/open-loops.md ✓ [N] active items Available registers: people.md [N] entries projects.md [N] entries decisions.md [N] entries preferences.md [N] entries tech-stack.md [N] entries Archive: [N] files Hooks: SessionStart [configured/not configured] PreCompact [configured/not configured]
4. Highlight Gaps
If expected files are missing:
Missing: ✗ CLAUDE.local.md — run /recall-init to create ✗ No daily log for today — will be created on first /recall-write
5. Quick Actions
Use /recall-search <query> to pull context from any tier. Use /recall-status for memory health metrics.
Stats
203
Stars
14
Forks
Quiet
Maintenance
Shell
Language
Last commit
Created
Ships withrecall
A memory system for Claude Code that remembers what matters and forgets what doesn't.
20310 skills
Stars on GitHub
Momentum
- stars in total
- 203
Other skills on recall.
@davegoldblattInstall Skillrecall-init-ids
Add durable IDs to memory entries. Required before /recall-maintain can run.
@davegoldblattInstall Skillrecall-init
Scaffold the Total Recall memory directory structure in this project.
@davegoldblattInstall Skillrecall-maintain
Pressure-based memory cleanup. Demotes, archives, or pins entries when working memory exceeds budget.
@davegoldblattInstall Skillrecall-promote
Review daily logs and promote entries to registers or working memory.
@davegoldblattInstall SkillMore skills from other plugins.
Auto-invoked
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
@obraInstall Skillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
@mattpocockInstall SkillAuto-invoked
Questions about recall-context.
- Which coding agents can use recall-context?
- recall-context installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.