Dev10x:memory-maintenance

To audit memory files, run a comprehensive scan across global, project, and plugin scopes to identify anti-patterns like stale paths, script-calling instructions, and contradictory instructions. The audit generates a categorized severity report for review.

Agents bypass skills due to memory health issues like stale references, version-pinned paths, or contradictory instructions. Auditing and cleaning up these memory anti-patterns resolves the bypass and restores instruction compliance.

Fix permission friction by scanning memory files for script-calling instructions and other anti-patterns. After identifying the conflicting instructions, execute a user-approved cleanup to remove them and restore proper skill integrity.

Yes, resolving memory health issues requires file system access and scripting capabilities to scan and modify memory files. The process also requires explicit user confirmation before executing any cleanup actions on the identified anti-patterns.

Run a memory maintenance audit regularly after plugin upgrades or when agents frequently bypass skills despite memory instructions. This ensures ongoing memory health, resolves stale references, and maintains compliance with skill integrity.