project-health

To audit Claude Code project permissions and configuration settings, you can run a project health check to scan `.claude/settings.local.json`, detect stale permission entries, identify MCP coverage gaps, and recommend fixes for context hygiene.

To set up baseline configuration for a new Claude Code project, you can initialize a project health workflow that automatically creates or refreshes `.claude/settings.local.json`, `CLAUDE.md`, and a safe `.gitignore`.

Context hygiene is the practice of evaluating your CLAUDE documentation footprint to detect stale references, overlaps, and oversized files, ensuring Claude Code has clean, high-quality context to prevent mid-task failures.

Yes, you can restructure oversized CLAUDE.md files by running a context quality audit, which evaluates the documentation footprint and proposes splitting the content into dedicated topic and rules files to meet size targets.

To scan for leaked secrets in your Claude Code project, you run a project health audit that performs targeted security scans across permissions and configuration files to detect and resolve exposed sensitive data.

You should capture session learnings in Claude Code persistent rules when you discover concise insights during a task, allowing the project health workflow to write them into `~/.claude/rules/` or `CLAUDE.md` to improve future continuity.