audit-memory

Audits agent instruction files, memory stores, and project docs for staleness, symbol errors, and context budget overruns.

54|6|Updated Jan 7, 2026
One-click install
npx skills add https://github.com/schmitthub/clawker --skill audit-memory-schmitthub
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: audit-memory
Source: https://github.com/schmitthub/clawker/tree/main/.agents/skills/audit-memory
Command: npx skills add https://github.com/schmitthub/clawker --skill audit-memory-schmitthub

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Agent instruction files (AGENTS.md), memory stores, and project documentation drift out of sync with the codebase over time, causing agents to follow outdated guidance, reference deleted symbols, and waste context budget on stale content. ## Core Features & Use Cases - Freshness and Symbol Accuracy Checks: Compares AGENTS.md commit dates against Go source changes and verifies that documented exported symbols still exist in the code. - Memory Graph Validation: Checks Serena memory files for broken mem: references, unindexed files, frozen dates, and stale project memories. - Context Budget and Contradiction Detection: Measures line counts against documented budgets and flags conflicting or duplicated instructions across always-loaded files. - Use Case: After a large refactor of the clawker CLI, run an audit to find AGENTS.md files documenting renamed functions, broken links in MEMORY.md, and docs exceeding the 200-line budget, then receive a prioritized DELETE/FIX/UPDATE action list. ## Quick Start Ask the agent to audit the project's agent instructions, memory files, and docs for stale or incorrect content.

Frequently Asked Questions about audit-memory

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

FAQPage Schema
How do I check if AGENTS.md files are out of date?▼

Run an audit that compares each AGENTS.md last commit date against the last commit date of Go files in its directory using git log. Files whose source changed after the instruction file was updated are flagged as stale.

How to find documented Go symbols that no longer exist?▼

The audit extracts backtick-wrapped exported identifiers from each package AGENTS.md and greps for them in the directory's Go source files. Identifiers documented but missing from source are reported as renamed or deleted.

Does this audit run automatically when editing memory files?▼

No. The skill is explicitly gated: it runs only when the user directly requests an audit of agent instructions, memory, or documentation. Reading or changing those files during other tasks does not trigger it.

What memory systems does the audit support?▼

It validates Serena memories in .serena/memories/ including mem: reference graphs, and Claude Code auto-memory under ~/.claude/projects/*/memory/. It does not assume other tools like Codex share that structure and reports limits when a source is unavailable.

What are the context budget limits for AGENTS.md files?▼

Root AGENTS.md plus always-loaded rules should stay under 500 lines, total always-loaded context under 800 lines, and each individual package AGENTS.md under 200 lines. Files exceeding these budgets are flagged with TRIM recommendations.