Env Doctor

What it does

Half a day disappears into setup sludge: a project that will not start, an env-var key nobody documented, a port owned by another service, or an install that went stale three branches ago. Env Doctor walks the usual failure points across Node, Python, Go, and Docker and tells you what is actually wrong.

Each finding includes a next step for the detected system: PowerShell on Windows or Bash on macOS and Linux. It compares environment-variable names and empty states without displaying values, identifies the owner of a busy port, and asks before any stop action. Nothing changes on your machine without you.

What it checks

• Missing dependencies and tools the project expects.
• Missing or empty environment-variable keys, without reading values into the report.
• Port conflicts, with PID, executable, and available service ownership evidence.
• Stale installs and lockfile drift.
• Runtime and version mismatches.
• A shell-specific next step for each problem it finds.

What the output looks like

Use the ordered startup checklist

The app-won't-run-locally guide shows how to preserve the first useful error, verify runtimes and lockfiles, compare environment-variable names without exposing values, identify the owner of a port, and hand a healthy environment into application-level diagnosis.

Questions