Menu

Individual skill

environment-config-auditor

Reviews .env/config files for consistency and missing required variables across environments. Use when comparing dev/staging/prod config, or debugging an "it works locally but not in prod" issue.

skills/utilities/environment-config-auditor/SKILL.md

Read pinned source

Source commit d0a9928d24afb7df0fad2f2f35f65d3938a6926a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
27
Repository last updated
Aug 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Purpose

Review environment/config files (`.env`, YAML/JSON config, etc.) for consistency across environments — missing variables, inconsistent naming, and unexplained differences that commonly cause "works locally, breaks in prod" bugs.

## When to Use

- Comparing config across environments (dev/staging/prod) to spot drift.
- Debugging an issue that only happens in one environment.
- Onboarding a new environment and want to confirm nothing's missing relative to existing ones.

## What to Analyze

1. **Missing variables** — a variable present in one environment's config but absent in another, where that's not obviously intentional (e.g. a `DEBUG` flag being dev-only is fine; a `DATABASE_URL` missing in prod is not).
2. **Naming inconsistency** — the same concept named differently across files (`DB_URL` in one, `DATABASE_URL` in another) — a common source of "I set the variable but it's not being picked up" bugs.