1. Validate Environment Completeness

Purpose: Check that .env.example contains all environment variables referenced in the codebase via process.env.*. Run after adding new env vars or when teammates report missing variable errors.

Prerequisites: None

Cost / Duration: $0 | ~15 sec

Prompt

Validate that .env.example is complete.

Step 1 — Run the completeness check:

```bash
bun run env:check-example
```

Scans source code for `process.env.*` references and compares against
`.env.example`. Reports any variables found in code but missing from
the example file.

Expected: Exit code 0 — `.env.example` is complete.

If a missing variable is reported, add it to `.env.example` with a
descriptive comment, then re-run the check.

Verification

  • bun run env:check-example exits with code 0
  • No missing variables reported
  • Any new env vars added to .env.example with descriptive comments

Back to index