actually-lsp-doctor

/actually-lsp-doctor

Parse the user's args from the invocation:

• fix as the first arg means skip the diagnostic report and jump straight to action.
• rust | typescript | ruby as an arg narrows focus to that ecosystem.
• No args: full diagnostic report followed by interactive fix.

Step 1: Read project state

Read .claude/actually-lsp.json in the current project root. If missing, run detection: source lib/detect.sh and lib/ecosystems.sh from the plugin root (the env var CLAUDE_PLUGIN_ROOT points there), call detect_ecosystems "$PWD", and for each detected ecosystem compute the current state per the rules in CONTEXT.md.

Step 2: Diagnose (unless fix arg present)

Output a per-ecosystem report. For each ecosystem:

• State (from CONTEXT.md's six states)
• For non-ready ecosystems: what's needed to reach ready
• For dismissed ecosystems: note them but don't propose action

Keep tone terse. No celebration messaging.

Step 3: Act

For each ecosystem in no-lsp-plugin, server-not-runnable, or error:

no-lsp-plugin: try claude plugin install <recommended_plugin>@claude-plugins-official via Bash. The user gets a permission prompt. If denied, output the slash command form (/plugin install <recommended_plugin>@claude-plugins-official) and ask the user to run it themselves.

server-not-runnable: run env fixes per ecosystem via Bash. All env fixes auto-run; the user has implicit project consent. Check readiness_source in the state file to aim the fix: binary means the server binary is missing or non-functional (fix the binary, not the deps); heuristic/probe means the binary ran but the project env needs work (build deps).

• TypeScript: npm install.
• Ruby: bundle install, plus gem install ruby-lsp if command -v ruby-lsp is empty.
• Rust: the binary is the usual culprit, and cargo build does NOT fix it. The rust-analyzer-lsp plugin launches a bare rust-analyzer from PATH, which is often a rustup proxy that is non-functional when the rust-analyzer component isn't installed for the active toolchain (rust-analyzer is unavailable for the active toolchain). Recover in order:
  1. Binary: if rust-analyzer --version fails or prints unavailable for the active toolchain (test it, don't trust command -v alone, since the proxy resolves but doesn't run), run rustup component add rust-analyzer. This makes the bare rust-analyzer the LSP tool launches actually work. If rustup is absent, tell the user to install rust-analyzer so a working binary is first on PATH (rustup component, mise, or brew) and stop.
  2. Standard library: rust-analyzer needs rust-src to load std; without it nav can return nothing. If rustc --print sysroot has no lib/rustlib/src, run rustup component add rust-src.
  3. Deps / proc-macros: cargo build so dependency and macro-generated symbols resolve (intra-project nav works without this, but full semantics need it). Then let Step 5 re-probe to confirm the server actually answers.