validate-config

Validate Config

ℹ️ First, set expectations: before anything else, print one short line with this skill's version and its most recent change — the top entry of metadata.changelog above — e.g. validate-config vX.Y — recent: <summary>. Then proceed.

Detect configuration drift across environment variable declarations. Ensures every variable used in code is declared in .env.example, and every declaration in docker-compose matches what the app actually needs.

State Dependencies

Source	Location	Read	Write	Description
Env example	.env.example	✅		Declared env vars with defaults
Docker Compose	docker-compose.yml, docker-compose.*.yml	✅		Container env declarations
Source code	src/	✅		Variables read at runtime
Config report	docs/reports/config-{date}.md		✅	Saved output

Process

Step 1: Extract Variables from .env.example

grep -E '^[A-Z_]+=|^# [A-Z_]+=' .env.example 2>/dev/null | grep -v '^#' | cut -d= -f1 | sort

Build a set: declared_vars.

Step 2: Extract Variables from docker-compose

# Extract env vars from all compose files
grep -rE '^\s+[A-Z_]+=|\$\{[A-Z_]+\}' docker-compose*.yml 2>/dev/null | grep -oE '[A-Z_]{2,}' | sort -u

Build a set: compose_vars.

Step 3: Extract Variables from Source Code

# Python: os.environ, os.getenv, settings.
grep -rn "os\.environ\[.\|os\.getenv(\|settings\." src/ 2>/dev/null | grep -oE "['\"][A-Z_]{2,}['\"]" | tr -d "'\""  | sort -u

# Node/JS: process.env.
grep -rn "process\.env\." src/ 2>/dev/null | grep -oE "process\.env\.[A-Z_]+" | sed 's/process\.env\.//' | sort -u

Build a set: code_vars.

Step 4: Compare .env.example vs Code

Find:

• In code but not in .env.example: Undocumented variables — operators won't know what to set
• In .env.example but not in code: Stale declarations — potentially safe to remove

# Set comparison (adapt to available shell tools)
comm -23 <(sort code_vars.txt) <(sort declared_vars.txt)  # in code, not declared
comm -23 <(sort declared_vars.txt) <(sort code_vars.txt)  # declared, not in code