Env Variable Safety Check
Compares environment variables referenced in code against .env files to find missing, unused, and security-risk variables. Also auto-generates a .env.example file.
/env-checkLead dev onboarding a new team member? Run /env-check to auto-generate .env.example and cut onboarding time
Production deploy owner? Quickly verify no required environment variables are missing before deploy
How It Works
Skill Code
Copy and paste into your CLAUDE.md to start using immediately.
How Env Variable Safety Check Works
Env Checker scans your codebase for environment variable references, cross-checks them against your .env files and .env.example, detects missing variables, unused definitions, and potential security issues like committed secrets.
When to Use Env Variable Safety Check
Critical before deployments when environment mismatches cause cryptic runtime errors — it catches the 'works on my machine' problems caused by missing or misconfigured environment variables across environments.
Key Strengths
- Detects missing environment variables before deployment
- Identifies unused .env entries that add confusion
- Warns about potential security issues with exposed secrets
- Cross-references all .env files for consistency