memory-hygiene

Audit and prune Claude Code auto-memory entries into ENFORCE, HOT, WARM, and STALE classes.

2|Updated Feb 23, 2026

Search Tags:#claude code #audit #memory #classification #archive #pruning

Ready to run

npx skills add https://github.com/MDGrey33/memnyx --skill memory-hygiene-mdgrey33

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: memory-hygiene
Source: https://github.com/MDGrey33/memnyx/tree/main/auto-memory/skills/memory-hygiene
Command: npx skills add https://github.com/MDGrey33/memnyx --skill memory-hygiene-mdgrey33

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill keeps Claude Code memory systems from becoming slow, noisy, or outdated by auditing, classifying, and pruning auto-memory content.

Core Features & Use Cases

Memory auditing: Counts entries, measures bloat, and inventories topic files and session summaries.
Lifecycle classification: Sorts items into ENFORCE, HOT, WARM, or STALE based on recency, validity, and duplication.
Safe cleanup and promotion: Archives stale content, proposes hard overrides for repeated failures, and can graduate durable knowledge into long-term records.
Use case: A workspace with dozens of memory notes and slow sessions can be reviewed in one pass, producing a clear report before any changes are made.

Quick Start

Ask the skill to audit the active project’s memory, classify each entry, and prepare a review-ready hygiene report.

Frequently Asked Questions about memory-hygiene

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

FAQPage Schema

How do I clean up Claude Code memory files to fix slow sessions?▼

To fix slow sessions, you can audit Claude Code memory files to count entries and measure bloat, then classify each item into ENFORCE, HOT, WARM, or STALE categories. This generates a review-ready report before any destructive pruning occurs.

What is the best way to prune auto-memory entries without losing important workspace notes?▼

The safest way to prune auto-memory entries is by classifying them by recency and validity first. Stale content is archived, immutable sources are preserved, and durable knowledge is promoted to long-term records before any deletion happens.

When should I run a memory audit on my Claude Code workspace?▼

You should run a memory audit when you notice slow-session remediation is needed or during periodic hygiene checks. If your workspace has dozens of topic notes and session summaries causing context bloat, a single audit pass can inventory and review them.

How does lifecycle classification work for session summaries and topic notes?▼

Lifecycle classification sorts session summaries and topic notes into ENFORCE, HOT, WARM, and STALE categories based on recency, validity, and duplication. This determines which entries are archived, promoted, or proposed for hard overrides.

Does the memory hygiene process automatically delete outdated workspace memory files?▼

No, the memory hygiene process does not automatically delete files. It prepares a review-ready hygiene report and performs classification before any destructive action, ensuring you can verify stale content archiving and hard overrides first.