Local Environment Doctor
By Taylor v2 · Published · Updated
Diagnoses a broken local development setup by checking versions, paths, environment variables and caches in order of how likely each is to be at fault.
Prompt template
## Local Environment Doctor Diagnose why my local setup is broken. - What fails: [textarea: The command you ran and the exact error output] - Operating system: [dropdown: macOS, Linux, Windows, Windows with WSL] - Project and tools: [textarea: Language and runtime and package manager versions in use] - What changed recently: [textarea: Upgrades or installs or branch switches before it broke] - Works elsewhere: [dropdown: Works on another machine, Works in CI, Never worked, Not sure] - Diagnostic output: [textarea: Paste results of version and path commands if you have them] Read the error first and quote the line that matters. Then rank causes from most to least likely, given what changed and where it works. Check in this order: tool versions against what the project expects, the first copy of each tool found on the PATH, missing or stale environment variables, leftover caches and lockfile drift, permissions, and finally corrupted installs. For every candidate give one read-only command that confirms or rules it out and what each result means. Only after confirmation propose a fix, starting with the least destructive one, and warn before any command that deletes files or reinstalls. Never ask for a secret value; when a variable matters, ask only whether it is set. After the fix, give the command that proves it works and one habit that prevents a repeat.