memory-auditor — Claude Code subagent: memory checks
The memory-auditor subagent for Claude Code checks memory against code and Git, flagging stale or duplicate entries. Run it after a major refactor.
no license ★ 276 updated 2026-10-29
/plugin marketplace add gupsammy/Claudest
/plugin install claude-memory@ClaudestWhat memory-auditor does
memory-auditor checks paths, functions, versions, settings, and conventions mentioned in memory against the project and Git history. It looks for deleted or renamed entities, changed behavior, and relative dates that have lost their meaning. Its tools are Read, Grep, Glob, and Bash(git:*).
The agent also spots overlapping entries and flags material that is outdated, repetitive, or too generic to guide future work. Code or Git evidence is required for factual findings; principles and preferences are judged against the memory corpus itself. When an entity is missing from the working tree, the agent checks whether it may belong to an external dependency before calling it stale.
For Claude Code, add the Claudest marketplace and install claude-memory@Claudest; the agent file path is .claude/agents/memory-auditor.md. Audits outside a Git repository have no project history to consult, so conclusions about changes need care.
What it helps with
- find memory references to deleted or renamed files
- check whether remembered versions and settings still match the project
- flag relative dates that need an absolute date
- catch disagreements between memory entries and code
- identify stale or duplicate entries to merge or remove
Example prompts for the agent
- Check the memory entries after this refactor and find stale file or function references.
- Compare the versions and settings in memory with the code and Git history.
- Find overlapping memory entries about this decision and suggest what to merge or remove.
How to install memory-auditor
1Plugin marketplace
/plugin marketplace add gupsammy/Claudest/plugin install claude-memory@Claudest2Manually: put the files in place
.claude/agents/memory-auditor.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/memory-auditor.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/memory-auditor.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about memory-auditor
How do I install memory-auditor in Claude Code?
Run /plugin marketplace add gupsammy/Claudest, then /plugin install claude-memory@Claudest. The agent file is at .claude/agents/memory-auditor.md.
What does memory-auditor do?
It checks memory entries against the current codebase and Git history, then flags stale facts, relative dates, and entries that may be merged or removed.
What evidence does memory-auditor use for factual findings?
It searches for files and definitions with Glob and Grep, checks versions in project manifests, and consults Git history. Factual findings require supporting evidence.