Stop "Works on My Machine" Frustration

Debugging environment configuration is one of the most tedious tasks for developers. This skill acts as a comprehensive diagnostic bridge between your local setup, containerized environments, and CI/CD pipelines. It automates the process of identifying why an application runs in one place but fails in another by analyzing the subtle layers of configuration that human eyes often miss.

What it does

The Environment Doctor performs a multi-layer audit of your project's configuration ecosystem. It doesn't just look at files; it builds a mental model of how your environment variables flow from development to production.

• Gap Analysis: Compares .env.example against local and CI configs to find missing dependencies.
• Security Auditing: Scans for accidentally committed secrets, hardcoded credentials, and weak production defaults.
• Version Parity: Detects mismatches between local runtime versions (Node/Python) and CI or Docker specifications.
• Path Validation: Identifies hardcoded absolute paths and cross-platform pathing issues that cause deployment failures.

Why use this skill?

Unlike a simple grep, this skill understands context. It knows the difference between a variable defined in a shell profile and one injected by GitHub Actions. It provides a structured Diagnosis Report that categorizes issues by severity, allowing you to fix onboarding blockers or security leaks in seconds rather than hours of troubleshooting.