audit-memory

Audit agent memory files for structural compliance and cross-file consistency.

9|1|Updated Jan 8, 2026
One-click install
npx skills add https://github.com/conn-castle/agent-layer --skill audit-memory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-memory
Source: https://github.com/conn-castle/agent-layer/tree/main/internal/templates/skills/audit-memory
Command: npx skills add https://github.com/conn-castle/agent-layer --skill audit-memory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit and fix the agent memory files (ISSUES.md, BACKLOG.md, ROADMAP.md, DECISIONS.md, COMMANDS.md, CONTEXT.md) for structural compliance, staleness, misplacement, cross-file consistency, and DECISIONS.md bloat. Use audit-documentation for repo documentation accuracy.

Core Features & Use Cases

  • Structural validation of all memory files against their documented templates.
  • Cross-file consistency checks to detect stale, duplicate, or misfiled entries.
  • DECISIONS.md consolidation guidance to remove redundancy while preserving tradeoffs.
  • Automated reporting of findings and tentative fixes to prepare for human review.

Quick Start

Run the audit-memory skill in your repository to generate the audit report and recommended actions.

Frequently Asked Questions about audit-memory

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

FAQPage Schema
How do I audit agent memory files for structural compliance and stale entries?

Cross-file consistency checks detect misplacements, stale entries, and duplicates across agent memory files such as BACKLOG.md and CONTEXT.md. The audit validates structural compliance against templates and generates a report with recommended actions and prioritized fixes.

What is the best way to consolidate DECISIONS.md bloat in a repository?

Consolidating DECISIONS.md bloat involves running an audit that identifies redundant entries and provides consolidation guidance to remove duplicates while preserving tradeoffs. The audit generates a final report at .agent-layer/tmp/ detailing recommended consolidations for human review.

How do I check if repository memory files like ROADMAP.md and BACKLOG.md have duplicate or misfiled entries?

Checking for duplicate or misfiled entries in ROADLOG.md and BACKLOG.md requires running a cross-file consistency audit that applies structural validation against documented templates. The audit identifies misplacements, stale entries, and duplicates, then generates a prioritized fix plan.

Does the memory file audit generate a report I can review before making changes?

The audit generates a final report at .agent-layer/tmp/audit-memory.<run-id>.report.md detailing structural findings, recommended actions, and potential DECISIONS.md consolidations. This report prepares tentative fixes for human review before changes are applied to memory files.

When should I use a dedicated memory audit instead of general documentation checks?

Use a dedicated memory audit when targeting agent memory files like ISSUES.md, DECISIONS.md, and CONTEXT.md for structural compliance and content freshness. For general repository documentation accuracy, use audit-documentation instead to verify standard docs.