memory-cleanup

Clean stale memory entries with a dry run preview before applying changes.

2|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/dmzoneill/skills --skill memory-cleanup
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: memory-cleanup
Source: https://github.com/dmzoneill/skills/tree/main/memory-cleanup
Command: npx skills add https://github.com/dmzoneill/skills --skill memory-cleanup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps maintain a clean and efficient memory by removing outdated or irrelevant information, such as closed issues, merged merge requests, and old session logs.

Core Features & Use Cases

  • Stale Entry Removal: Automatically identifies and removes closed issues, merged MRs, and expired namespaces.
  • Session Log Archival: Compresses and archives old session logs to save space.
  • Use Case: Run this skill periodically to ensure your system's memory is free of clutter, improving performance and reducing storage usage.

Quick Start

Run a dry run of the memory cleanup skill to see what would be removed.

Frequently Asked Questions about memory-cleanup

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

FAQPage Schema
How do I clean up stale memory entries like closed issues and merged merge requests?▼

Memory cleanup removes stale entries like closed issues, merged merge requests, and expired ephemeral namespaces by scanning memory and performing a dry run by default to preview changes before applying them.

What is the best way to archive old session logs to save space?▼

Archiving old session logs is handled by memory cleanup, which compresses and archives old session logs to save space and reduce storage usage.

Can I preview what gets removed before applying memory cleanup?▼

Yes, memory cleanup performs a dry run by default, allowing you to preview changes including removed stale entries, closed issues, and merged MRs before applying them.

How does removing expired ephemeral namespaces improve system performance?▼

Removing expired ephemeral namespaces improves performance by ensuring memory is free of clutter, reducing storage usage, and maintaining an efficient system.

Do I need specific memory read operations to perform stale entry removal?▼

Yes, stale entry removal requires specific memory read operations and file system interactions for cleanup and archival of outdated information and old session logs.

When should I run memory cleanup to maintain an efficient system?▼

You should run memory cleanup periodically to maintain a clean and efficient system, ensuring stale entries, merged MRs, and old session logs are removed before accumulating and degrading performance.