env-health-check

To diagnose environment hangs like stuck git locks or a wedged Docker daemon, you can run a unified environment health check. It probes local development states using timeout-wrapped checks and outputs a prioritized P0–P3 punch list separating safe auto-fixes from required user actions.

Your Xcode simulator may stall due to environment-level state issues like corrupted DerivedData. An environment health check probes simulator state and disk capacity, helping you rule out environment-caused failures before investigating your project code.

The best way to troubleshoot MCP server timeouts and stalled plugin loading is to perform an ordered environment diagnostic sweep. This checks MCP servers and plugin loading states, identifying whether persistent issues stem from local environment friction rather than application bugs.

Yes, you can automatically remove stale git lockfiles during an environment health check. The diagnostic safely prunes stale lockfiles and worktree entries only when no owning git process exists, while leaving risky actions like Docker daemon restarts to the user.

Yes, the environment diagnostics check is macOS-compatible and specifically probes disk capacity to rule out disk pressure. It uses ordered timeout-wrapped probes to safely identify near-full system volumes that may cause development friction.

You get a P0–P3 punch list for local development environment failures by running a unified end-to-end environment sweep. This structured diagnostic evaluates git, Docker, Xcode, MCP servers, and disk space, outputting severity-ranked actions to resolve environment-level issues.