audit-claude-setup

Auditing your Claude Code configuration involves inventorying local and global setups like CLAUDE.md and .mcp.json, fetching official documentation, comparing states, and generating a prioritized remediation plan with exact file paths.

A Claude Code setup inventory captures CLAUDE.md, per-project and global settings, .claude/skills/, .claude/agents/, and .mcp.json files to detect configuration gaps against the latest official documentation.

Generating a remediation plan for outdated Claude Code settings requires comparing features, hooks, and permissions against the latest official documentation, then producing a prioritized list of concrete steps with exact dotfile-repo paths.

Yes, the Claude Code configuration audit applies to both local and global setups, inventorying settings, skills, agents, and MCP definitions to detect configuration gaps across your entire environment.

Your Claude Code configuration may be missing new features and hooks because your local setup has not been aligned with the latest official documentation, requiring a state comparison to detect gaps and deprecated items.

The best way to align Claude Code MCP and settings with new documentation is to snapshot your current configuration, compare it against the latest official docs, and apply a prioritized remediation plan to adopt new features or remove deprecated items.