Environment Contract Drift Fixer

The problem

Environment variables often drift between local development, Docker configs, CI workflows, and deployment documentation. This causes "works on my machine" failures, broken handoffs, and production outages when renamed or missing variables go unnoticed.

What it does

• Audits the entire repository to map environment variable usage across code, config loaders, schemas, and documentation.
• Identifies missing, unused, renamed, legacy, or ambiguous variables.
• Proposes a canonical environment contract to resolve naming conflicts.
• Generates safe patches for .env.example, READMEs, and Docker files using only placeholders.
• Adds guardrails like startup validation and CI drift checks to prevent future inconsistencies.

Frameworks & tools

Works with any stack including Node.js, Express, Prisma, Next.js, Docker, GitHub Actions, and platforms like Vercel or Render.

Why this beats prompting it yourself

Manual auditing is error-prone and often misses variables hidden in CI YAMLs or deployment notes. This skill enforces a structured workflow that creates a source register, ensuring no variable is overlooked while strictly protecting you from accidental secret exposure in logs or docs.

Use cases

• Standardize environment variable names before a major client handoff.
• Fix deployment failures caused by inconsistent naming between code and hosting providers.
• Clean up legacy variables after a refactor or platform migration.
• Add automated checks to ensure .env.example never falls out of sync with the code.

Known limitations

Cannot access live hosting dashboards, cloud secret stores, or production logs. It does not handle real secret rotation or validate the values of secrets themselves.