system-audit

To audit a Claude Code setup, run the /audit command to scan local and linked project files. It checks skills, memory, settings, hooks, and docs for drift, missing entries, and broken cross-references, returning a scorecard with prioritized action items.

A Claude Code configuration audit verifies frontmatter, file existence, index coverage, permissions, executable scripts, and cross-references. It identifies configuration errors, stale settings, and inconsistent business context across local and linked project files.

Claude Code skills and memory files fall out of sync due to drift, missing entries, or stale configuration. An audit checks file existence, frontmatter, and cross-references to locate these inconsistencies and generate an action item list for cleanup.

Yes, you can perform a read-only audit of Claude Code hooks and settings. The audit safely inspects executable scripts, permissions, and configuration entries without modifying the workspace, producing a scorecard and warnings for any issues found.

To verify Claude Code frontmatter and executable script permissions, run an audit scan. It checks frontmatter consistency, validates file permissions, verifies executable scripts, and reports any date-sensitive issues or missing index coverage in a structured report.

The best way to fix broken links and missing entries in Claude Code is to run an audit that produces a scorecard, issue table, and prioritized action items. Use this read-only report to systematically clean up configuration drift and file inconsistencies.