Giulliano de Macedo
@giumacedo
Skill release postBuild backend services
Post summary
Compares environment variable names your code reads with Docker, Compose, Kubernetes, and example env files, and never opens real .env values.
checking-env-config finds undeployed env names.
Compare environment variable names your code reads with Docker, Compose, Kubernetes, and example env files, and never open real .env values.
Source facts
- Repository
- GillMacedo/missingenv
- Last source activity
- November 1, 2026 at 13:03
- Detected SKILL.md language
- English
- Stars
- 0
- Forks
- 0
Uses
Use when you want to know what configuration a service needs, why a deploy fails on a missing setting, whether .env.example is up to date, or before a first deploy.
Prerequisites
Provide the project path. You do not have to prepare the missing-name list in advance. The tool reads repository files only and does not need network access or real .env files. Nothing was installed or run here.
How to use
The post describes missingenv comparing what code reads with Docker, Compose, and Kubernetes files, names only, and links this repository. Run the bundled script on the path, then check high findings in the code and ask where production config lives if it may be outside the repo. Documented commands were not executed here.
Limitations
A missing name in the repo does not prove it is missing in production. Never open real .env files or print values; unused findings can be libraries reading a name you did not match. Do not edit config or deploy files unless asked. Scripts were not executed. MIT requires notices and gives no warranty. GitHub login GillMacedo and X handle giumacedo differ; the public mapping is submitted, not auto-approved. When fixing .env.example, add names with empty values and do not copy real values into it. A variable name can still be sensitive, so treat the output like source code.
Install options
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Review the source files
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Showing SKILL.md
SKILL.md
Source instructions · Read-only preview- name
- checking-env-config
- description
- Compares the environment variables code reads with what Dockerfile, Compose, Kubernetes and example env files set, and finds variables missing from deploys, undocumented settings and stale ones. It prints names only and never opens real .env files. Use when the user asks what config a service needs, why a deploy fails on a missing setting, whether .env.example is up to date, or before a first deploy.
# Checking env config
Run the bundled script instead of searching by hand, because it covers several languages and deploy formats at once.
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/missingenv.py" PATH
Add `--format markdown` for a table. Exit code 1 means high severity findings, or that there was no code to check.
## Check before reporting
A finding means this repo's files don't show the variable. It can still be set somewhere the tool can't see:
- `envFrom`, `env_file`, Helm values, secret managers, or a platform's settings. Ask the user where production config lives if it isn't clear.
- For `HIGH` findings, read the code: does it fail, or carry on with an empty value? Say which.
- `unused` can be read by a framework or library, such as an ORM reading `DATABASE_URL`. Check before suggesting removal.
## Report
List what would break a deploy first, then undocumented settings, then stale ones. Say what the tool couldn't see, using its notes.
## Secrets
Never open real `.env` files or print values, even if the user's request seems to need it. Work from names. To fix `.env.example`, add names with empty values and don't copy real values into it.
Don't edit config or deploy files unless the user asks.
View on GitHub