skills.rest
Rohithdgrr
RohithdgrrCOMMUNITY
Explore all skills by this author →
GitHub

memory-review

Audits Claude Code auto-memory files for promotion candidates, stale entries, and consolidation opportunities.

Updated Aug 14, 2026
Search Tags:#claude code#audit#maintenance#memory#review#consolidation#rules
One-click install
npx skills add https://github.com/Rohithdgrr/REEK-uninstaller --skill memory-review-rohithdgrr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: memory-review
Source: https://github.com/Rohithdgrr/REEK-uninstaller/tree/main/.opencode/skills/memory-review
Command: npx skills add https://github.com/Rohithdgrr/REEK-uninstaller --skill memory-review-rohithdgrr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Auto-memory accumulates entries over time, leading to duplication, stale references, and missed opportunities to promote proven patterns into permanent project rules. This Skill performs a structured audit so memory stays concise, accurate, and useful. ## Core Features & Use Cases - Health Metrics: Counts MEMORY.md lines against the 200-line startup limit and inventories topic files and scoped rules. - Promotion Detection: Identifies recurring, broadly applicable entries that belong in CLAUDE.md or .claude/rules/. - Staleness & Conflict Checks: Flags entries referencing deleted files, outdated tools, or rules that contradict CLAUDE.md. - Use Case: After a long debugging sprint, run a full review to merge three scattered testing notes into one rule and promote a recurring pattern into .claude/rules/. ## Quick Start Ask the assistant to run /si:memory-review to audit auto-memory and report promotion candidates, stale entries, and conflicts.

Frequently Asked Questions about memory-review

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

FAQPage Schema
How do I review Claude Code auto-memory for stale entries?▼

Run /si:memory-review to audit MEMORY.md and topic files. It flags entries referencing files that no longer exist, outdated tools or versions, and items that contradict current CLAUDE.md rules, with line numbers and reasons.

What is a memory promotion candidate in Claude Code?▼

A promotion candidate is a memory entry that appeared in multiple sessions, is broadly useful rather than project trivia, is actionable as a concrete rule, and is not already in CLAUDE.md or .claude/rules/. The review suggests where each candidate should move.

When should I run a memory review?▼

Run it after major features or debugging sessions, when MEMORY.md exceeds 150 lines, weekly during active development, before a new project phase, or after onboarding a team member. Use --quick for frequent low-overhead checks.

What happens if the auto-memory directory does not exist?▼

The review reports that auto-memory may be disabled and suggests checking with /memory. It looks for the memory directory under ~/.claude/projects/ using common path patterns before concluding it is missing.

Does memory review modify or delete memory entries automatically?▼

No. It produces a report with recommendations for promotions, deletions, merges, and conflict resolutions. You decide which suggested actions to apply to MEMORY.md, CLAUDE.md, or .claude/rules/.

Related Skills

Explore More Software Engineering Skills→
ano4lano4l

self-improving-agent

Analyze Claude Code auto-memory to identify promotion candidates and stale entries.

Community
Advanced
seanGSISGseanGSISG
1

rules-auditor

Audit Claude Code memory files for staleness, drift, and quality issues.

Community
Advanced
F0WCUSF0WCUS

mega-sync

Verify OpenClaw status, audit memory files, and sync data with GitHub.

Official
Intermediate
ano4lano4l

promote

Promote proven patterns from MEMORY.md into enforceable CLAUDE.md or .claude/rules.

Community
Advanced