audit-memory

Validate MEMORY.md index consistency across project memory directories.

2|Updated Dec 20, 2020
One-click install
npx skills add https://github.com/buvis/home --skill audit-memory-buvis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-memory
Source: https://github.com/buvis/home/tree/main/.claude/skills/audit-memory
Command: npx skills add https://github.com/buvis/home --skill audit-memory-buvis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Memory indexes across projects can become inconsistent, with missing or stale entries that confuse maintenance and auditing. This Skill identifies and flags inconsistencies, enabling clean and reliable memory governance across projects.

Core Features & Use Cases

  • Validates MEMORY.md indexes for project memories and identifies orphaned references.
  • Compares actual memory files on disk against index entries to surface missing or extra entries.
  • Reads memory files' YAML frontmatter to capture type, name, and descriptions for governance and cleanup actions.
  • Produces a structured audit report to guide remediation and governance.

Quick Start

Run a memory audit across all projects to surface orphan and stale entries and generate a remediation plan.

Frequently Asked Questions about audit-memory

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

FAQPage Schema
How do I check memory index consistency for orphan and missing entries?

To check memory index consistency, you need to parse MEMORY.md frontmatter and compare actual memory files on disk against index entries to detect and report orphan and missing entries for remediation.

What causes stale or orphan entries in project memory directories?

Stale or orphan entries occur when memory files are deleted or moved on disk without updating the MEMORY.md index, causing the index to reference missing files or contain outdated metadata.

How do I audit MEMORY.md files across multiple projects?

You can audit MEMORY.md files across projects by scanning ~/.claude/projects/*/memory directories to validate index entries against actual files and generate a structured staleness report.

Does the memory audit read YAML frontmatter from individual memory files?

Yes, the memory audit reads YAML frontmatter from individual memory files to capture type, name, and descriptions for accurate governance and cleanup actions.

What is the best way to surface missing memory index entries for remediation?

The best way to surface missing memory index entries is to compare disk files against MEMORY.md indexes, categorize staleness by type, and produce a structured audit report to guide remediation.