memory-clean

Audit memory directories for structural integrity and staleness against session histories.

5|2|Updated Nov 17, 2025
One-click install
npx skills add https://github.com/OutlineDriven/odin-gemini-cli-extension --skill memory-clean
Or copy as Structured Prompt for Agentโ–ผ
Please help me install this Agent Skill.
Skill: memory-clean
Source: https://github.com/OutlineDriven/odin-gemini-cli-extension/tree/main/skills/memory-clean
Command: npx skills add https://github.com/OutlineDriven/odin-gemini-cli-extension --skill memory-clean

SYSTEM DOCUMENTATION & REQUIREMENTS

๐Ÿ’ก This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Audits memory directories for structural rot and staleness against session-history transcripts, identifying orphans, dangling references, duplicates, missing sections, and oversized entries, and surfaces issues for review before fixes.

Core Features & Use Cases

  • Audits memory structures to surface orphans, dangling entries, near-duplicates, and missing frontmatter sections.
  • Checks staleness by comparing memory rules against recent session evidence to flag outdated commitments.
  • Recommends safe fixes and requires user confirmation before applying changes to preserve data integrity.

Quick Start

Run memory-clean to audit your memory directory and begin reviewing the recommended fixes.

Frequently Asked Questions about memory-clean

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

FAQPage Schema
How do I audit memory directories for structural integrity and staleness?โ–ผ

To audit memory directories, run memory-clean to cross-check memory rules against session-history transcripts, surfacing orphans, dangling references, and outdated commitments for review before applying fixes.

What causes orphaned, duplicated, or outdated memories in memory repositories?โ–ผ

Orphaned, duplicated, or outdated memories occur when memory repositories lack consistent frontmatter enforcement and fail to cross-check against session-history transcripts, leading to structural rot and stale commitments over time.

Can I detect credentials leakage and missing frontmatter sections in memory files?โ–ผ

Yes, you can detect credentials leakage and missing frontmatter sections by running memory-clean, which enforces frontmatter completeness and scans for risky patterns, producing a prioritized report of structural issues.

How do I fix stale memory rules flagged during a memory hygiene audit?โ–ผ

To fix stale memory rules, review the prioritized report generated by memory-clean, which recommends safe fixes based on session-history evidence, and apply changes only after user confirmation to preserve data integrity.

Does memory-clean apply fixes automatically to memory repositories?โ–ผ

No, memory-clean does not apply fixes automatically; it requires user confirmation before applying any recommended changes to memory repositories, ensuring data integrity and preventing unintended modifications to memory rules.

What's the best way to identify fix-recipe patterns in session-history transcripts?โ–ผ

The best way to identify fix-recipe patterns is to run memory-clean, which detects these patterns during its audit and cross-references them with session histories to flag risky or stale memories requiring review.