audit

You can detect redundant or contradictory memories by running a vault integrity audit that checks memory consistency, index completeness, and link validity, outputting a numbered report grouped by checklist sections.

You should run a memory audit approximately every 7 sessions or when your briefing indicates an audit-due flag, ensuring accumulated notes and skills have not become stale, contradictory, or incorrectly referenced over time.

Vault integrity checking prevents skill drift by auditing each skill's SKILL.md to catch outdated patterns or references, flagging mismatches between what skills claim and what the vault actually supports.

The best way to validate wikilinks and markdown links is performing a deterministic read-mostly analysis that traverses memory and skill files, ensuring all vault references still resolve correctly.

The audit skill does not fix index drift automatically; it produces a structured numbered report grouped by checklist sections, allowing you to review the findings and choose which fixes to apply.