midnight-expert:doctor

Run diagnostics by launching concurrent background scripts that check plugin health, MCP servers, external CLI tools, cross-plugin references, and NPM registry reachability. The system parses CHECK_NAME | STATUS | DETAIL output into a unified health report with PASS/WARN/FAIL badges.

Yes, you can automatically repair MCP servers and plugin installations using the optional --auto-fix mode. It uses interactive fix prompts driven by platform-aware recipes and re-verifies only affected checks after applying remediation.

A full health check requires python3, curl, npm, npx, node, git, gh, docker, jq, tsc, nvm, and claude installed. These external CLI tools are assessed alongside cross-plugin references and NPM registry reachability during diagnostics.

NPM registry reachability checks fail when network policies or proxy configurations block access. The diagnostic script tests registry connections and reports the failure status, allowing the platform-aware fix-table to suggest appropriate remediation steps.

Yes, the diagnostic tool works for both local developer machines and CI environments. It assesses plugin installations, MCP servers, and external CLI tooling, providing platform-aware remediation recipes that adapt to the specific operating environment.

The best way to troubleshoot broken cross-plugin references is running concurrent diagnostic scripts that assess plugin health and dependencies. The structured health report identifies WARN or FAIL statuses, offering guided remediation through platform-aware fix-table recipes.