Detect config drift between required local env keys and a Render service before deploy; fails when required keys are missing remotely.
Use this skill before deploy to compare required environment keys with what is currently configured on a Render service.
RENDER_SERVICE_ID or RENDER_SERVICE_NAMEREQUIRED_ENV_KEYS or local env template filesRENDER_API_KEY (required unless using mock JSON)RENDER_SERVICE_IDRENDER_SERVICE_NAMERENDER_API_BASE_URL (default https://api.render.com/v1)REQUIRED_ENV_KEYS (comma-separated explicit required keys)REQUIRED_ENV_FILES (comma-separated files to parse, default .env.example,.env.production)RENDER_ENV_VARS_JSON_PATH (path to saved Render env-var API JSON for offline testing)bash scripts/render-deploy-diff.sh
With explicit required keys:
RENDER_SERVICE_NAME=my-service \
REQUIRED_ENV_KEYS="DATABASE_URL,DIRECT_URL,SHADOW_DATABASE_URL,NEXT_PUBLIC_APP_URL" \
bash scripts/render-deploy-diff.sh
Offline test with saved API response:
REQUIRED_ENV_KEYS="DATABASE_URL,NEXT_PUBLIC_APP_URL" \
RENDER_ENV_VARS_JSON_PATH=./fixtures/render-env-vars.json \
bash scripts/render-deploy-diff.sh
0 when all required keys exist on Render1 when required keys are missing or inputs are invalidZIP package — ready to use