Recipes Core Pack · Ops

Environment Variable Audit Recipe

Compare local/CI/hosting variables in one pass and quickly surface gaps and security issues.

Practical tip

If sharing values is risky, provide key names only and mask sensitive values.

Environment Audit Prompt

Copy and use

"I want to audit environment variables across environments. Use the inputs below to detect missing keys, typos, and security risks. [Inputs] - Local files: [.env, .env.local, .env.production, etc.] - CI/CD variables: [CI_ENV_LIST] - Hosting platform variables: [HOSTING_ENV_LIST] - Framework: [Vite/Next.js/FastAPI/other] [Output requirements] 1) Environment matrix table (local/staging/prod) 2) Missing keys and typos 3) Client-exposure risks for sensitive values 4) .env.example draft 5) Priority plan (P0/P1/P2)"

Copy this prompt and paste it into your AI chat.

.env.example sample

.env.example

# Frontend
VITE_API_URL=

# Backend
DATABASE_URL=
JWT_SECRET=

# Optional
SENTRY_DSN=

Execution Checklist

0/5 done

Collect variable inventoryList local, CI, and hosting keys

Validate framework prefixesCheck VITE_, NEXT_PUBLIC_, etc.

Check secret exposure riskEnsure server-only keys stay server-side

Update .env.exampleInclude required keys and descriptions

Rebuild/redeploy verificationValidate runtime values

Environment Variable Issue

Runtime undefined troubleshooting

Failed to fetch

API URL misconfiguration checks

Last updated: February 22, 2026 · Version: v0.0.1

Send Feedback

Opens a new issue page with your message.

Open GitHub Issue