env-doctor
Eliminates time spent diagnosing GPU/CUDA misconfigurations across development, containerized, and CI/CD environments—reducing deployment failures and accele…
Diagnose and Fix CUDA / GPU environments compatibility issues locally, in Docker, and CI/CD. CLI + MCP server available.
- Ask Claude to diagnose GPU compatibility issues in your local CUDA environment quickly.
- Generate Docker configuration fixes for mismatched CUDA and GPU driver versions.
- Automate GPU environment validation in CI/CD pipelines to prevent deployment failures.
Eliminates time spent diagnosing GPU/CUDA misconfigurations across development, containerized, and CI/CD environments—reducing deployment failures and accelerating ML/compute workload onboarding.
Infrastructure and ML engineering teams managing GPU-dependent applications across multiple deployment contexts.
https://github.com/mitulgarg/env-doctor
By mitulgarg
How to Get It
claude plugins install mitulgarg/env-doctor
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.
After installing, paste this into Claude:
Diagnose GPU compatibility issues in my local CUDA environment quickly
Trust Signals Auto-scanned
Community Pulse Active
Discussed on Hacker News, Reddit
- [Security] Claude Code reads .env files by default - This needs immediate attent — Reddit · 320 pts
- Is my GRPO LLM training on my ETL-Doctor-Pipeline-Env working? — Reddit · 1 pts
- Is my GRPO LLM training on my ETL-Doctor-Pipeline-Env working? — Reddit · 1 pts
3 mentions across 1 sources
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
catalog_hygiene stale-eval refresh: Scored from trust signals (evidence-eval-v1): 171 GitHub stars; 4 contributors; last commit 17d ago; license MIT.
Things to check
- Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
catalog_hygiene stale-eval refresh: Scored from trust signals (evidence-eval-v1): 171 GitHub stars; 4 contributors; last commit 17d ago; license MIT.