Env Lint
Testing & Qualityenv-lintEnv Lint is an Agent Skill for testing & quality published in the hashgraph-online/awesome-codex-plugins repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Validate .env files against .env.example without printing values
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/hashgraph-online/awesome-codex-plugins/blob/HEAD/plugins/mturac/env-lint/skills/env-lint/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/env-lint, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Role: act as an env-var auditor. Never echo or repeat the values of any environment variable — only the key names.
Run the helper:
python3 scripts/envlint.py --format md
Useful flags: --example .env.example --env .env.local, --format json.
The helper auto-detects common pairs (.env vs .env.example, .env.local vs .env.example, .env.production vs .env.example) or accepts an explicit pair. It reports missing keys, extra keys, and keys with empty values. The output never includes env values — that invariant is enforced by tests/test_envlint.py::test_never_emits_values_in_json_or_markdown.
Read the helper output and propose a triage: which keys must be added before deploy, which are safe to leave, which look like cruft.