skills.rest
Zeyad-37
Zeyad-37COMMUNITY
Explore all skills by this author →
GitHub

audit-memory

Audit Claude Code auto-memory files for stale, duplicate, or wrong entries.

Updated Apr 21, 2026
Search Tags:#claude code#maintenance#cleanup#memory audit#stale entries#memory store#session hook
One-click install
npx skills add https://github.com/Zeyad-37/tech-agency --skill audit-memory-zeyad-37
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: audit-memory
Source: https://github.com/Zeyad-37/tech-agency/tree/main/.claude/skills/audit-memory
Command: npx skills add https://github.com/Zeyad-37/tech-agency --skill audit-memory-zeyad-37

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Claude Code's auto-memory store accumulates entries over time that can become stale, duplicated, or factually wrong, causing false facts to propagate into future sessions. This Skill provides a structured periodic audit to catch and fix those memories before they mislead the agent. ## Core Features & Use Cases - Memory Store Discovery: Locates the per-project memory directory under $HOME/.claude/projects/<encoded-path>/memory, with support for a CLAUDE_MEMORY_DIR override for non-default locations. - Four-Question Evaluation: Checks each memory file for truthfulness, usefulness, specificity, and uniqueness, then proposes KEEP, DELETE, MERGE, or EDIT verdicts in a review table. - Approval-Gated Changes: Proposes all modifications first and waits for explicit user approval before editing files or updating the MEMORY.md index. - Audit Stamping: Writes the audit date to .claude/.last-memory-audit so the SessionStart reminder hook stays quiet for 30 days. - Use Case: After a major refactor that renamed modules and shipped old features, run the audit to delete project memories referencing deleted code and merge overlapping feedback memories. ## Quick Start Ask Claude to audit memory and review the proposed verdict table before approving any changes.

Frequently Asked Questions about audit-memory

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit Claude Code memory files?▼

Run the audit-memory skill, which locates the memory store at $HOME/.claude/projects/<encoded-project-path>/memory, reads each file listed in MEMORY.md, and proposes KEEP, DELETE, MERGE, or EDIT verdicts. Changes are applied only after your approval.

Where does Claude Code store auto-memory files?▼

Memories live outside the project in $HOME/.claude/projects/<encoded-project-path>/memory, where the encoded path replaces slashes and dots with dashes. The MEMORY.md file in that directory indexes all active memory files.

How often should I audit Claude Code memories?▼

The default cadence is every 30 days, tracked via the .claude/.last-memory-audit stamp file. Trigger an early audit after major refactors or when a feedback memory is being consistently overridden.

What if my Claude memory is stored in a custom location?▼

Set the CLAUDE_MEMORY_DIR environment variable to your custom path before running the audit. The skill checks this override first and falls back to the default $HOME/.claude/projects location.

Does the memory audit delete files automatically?▼

No. The audit only proposes changes in a verdict table and waits for explicit per-change user approval before editing or deleting any memory file or updating the MEMORY.md index.

Related Skills

Explore More Software Engineering Skills→
arbisoftarbisoft
4

ck

Load and save per-project context.json and CONTEXT.md for Claude Code sessions.

Official
Advanced
OutlineDrivenOutlineDriven
5

memory-update

Scan session transcripts to extract save-worthy moments and write memory files.

Official
Advanced
CarlosQ96CarlosQ96

sprint-status

Read sprint plans and story files to summarize progress and flag risks.

Community
Advanced
onebrain-aionebrain-ai
23

memory-review

Audit and prune persisted memory entries by reviewing MEMORY-INDEX.md files.

Official
Advanced