Compares environment variable names your code reads with Docker, Compose, Kubernetes, and example env files, and never opens real .env values.
checking-env-config
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.
Datos de origen
- Repositorio
- GillMacedo/missingenv
- Última actividad en el origen
- 1 de noviembre de 2026 a las 13:03
- Idioma detectado de SKILL.md
- inglés
- Estrellas
- 0
- Forks
- 0
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.
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.
Opciones de instalación
De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.
Revisa los archivos de origen
Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.
Mostrando SKILL.md
- 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.