startup-diagnostic

To diagnose Claude Code startup issues, run a health check that validates configuration files, hook execution, MCP server connectivity, and filesystem integrity. It reports PASS, FAIL, or WARN for each component and suggests actionable fixes for identified problems.

Your Claude Code environment may fail to start due to misconfigured settings, broken hooks, outdated indexes, or filesystem integrity issues. A startup diagnostic pinpoints the exact failing component and provides specific fixes to restore normal operation.

A Claude Code health check verifies configuration files, hook execution, MCP server connectivity, indexing, filesystem structure, Git health, sandbox settings, plugin loading, skill file integrity, and vault review readiness, reporting a status for each.

Yes, you can validate MCP server connectivity and JSON parsing by running a startup diagnostic. It tests server connections, checks JSON and markdown parsing validity, and reports failures with suggested fixes to ensure proper component functioning.

To troubleshoot broken hooks and outdated indexes in Claude Code, run a diagnostic health check. It validates hook script execution, checks index freshness, and reports any failures or warnings with actionable suggestions to resolve the issues.

The best way to perform a comprehensive health check on your Claude Code setup is to run a startup diagnostic. It systematically verifies configuration, hooks, MCP servers, indexes, plugins, and directory structures, then reports status and suggests fixes for failures.