Compares the environment variables a service actually reads (process.env, import.meta.env, os.environ, os.getenv, destructuring, with or without defaults) against .env.example and against the variable NAMES exported from each deployed environment, to catch launch-day config failures.
Compares the environment variables a service actually reads (process.env, import.meta.env, os.environ, os.getenv, destructuring, with or without defaults) against .env.example and against the variable NAMES exported from each deployed environment, to catch launch-day config failures - a required variable missing in production, a secret shipped to the browser through a NEXT_PUBLIC_/VITE_/REACT_APP_ prefix, staging and production running different configs, and stale credentials nobody reads. Use when someone asks "are all our env vars set in production", "did we forget a config var", "is any secret exposed to the frontend", "compare staging and production config", or as the sixth step of a production readiness review. Do NOT use to read, copy or rotate secret values; it only ever handles names. It does not see config loaded through typed wrappers it cannot parse (t3-env `env.X`, pydantic `BaseSettings`, SvelteKit `$env/static/private`, a secrets manager at runtime); list those names by hand.This is the skill's description: the text your AI reads to decide when the skill applies.
This is the skill's header. The step-by-step instructions are paid content and aren't shown here.
config-drift/SKILL.md
---
name: config-drift
description: Compares the environment variables a service actually reads (process.env, import.meta.env, os.environ, os.getenv, destructuring, with or without defaults) against .env.example and against the variable NAMES exported from each deployed environment, to catch launch-day config failures - a required variable missing in production, a secret shipped to the browser through a NEXT_PUBLIC_/VITE_/REACT_APP_ prefix, staging and production running different configs, and stale credentials nobody reads. Use when someone asks "are all our env vars set in production", "did we forget a config var", "is any secret exposed to the frontend", "compare staging and production config", or as the sixth step of a production readiness review. Do NOT use to read, copy or rotate secret values; it only ever handles names. It does not see config loaded through typed wrappers it cannot parse (t3-env `env.X`, pydantic `BaseSettings`, SvelteKit `$env/static/private`, a secrets manager at runtime); list those names by hand.
---
… the full instructions are part of a premium pack and load in your AI once you have access.