KeyanVakil/env-doctor

Find every env var the app uses and make them impossible to miss.

Steps

1. Search the codebase for all process.env., os.environ, import.meta.env., env() calls, or equivalent.
2. For each unique variable found, determine:
   • Is it required or optional?
   • What does it do? (infer from name + usage context)
   • What's the expected format? (URL, API key, boolean, number, etc.)
   • Is there a safe example value or should it say <your-value-here>?
3. Check if a .env.example already exists — update it rather than replace it if so.
4. Generate/update .env.example with every variable, grouped by service, with comments:

# Database
DATABASE_URL=postgresql://user:password@localhost:5432/mydb

# Auth
NEXTAUTH_SECRET=<generate with: openssl rand -base64 32>
NEXTAUTH_URL=http://localhost:3000

# External APIs
OPENAI_API_KEY=sk-...

5. Cross-check: flag any variable that appears in .env.example but isn't used in code (stale), and any used in code but missing from .env.example (dangerous).

Output

• Updated .env.example file
• Summary: total vars found, any stale, any missing, any that look like they might be secrets accidentally in source