env-lint

SkillFiles & storage

Validate .env files against .env.example without printing values

Use env-lint in Claude, ChatGPT or Ahel Desktop

Free. Sign in, add env-lint and connect your AI. About a minute.

Also: Claude Code · Cursor · Codex

Then ask your AI: use the env-lint skill

Details

Instructions available. Your AI can read the instructions. Execution depends on the setup they require.

Add ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.

env-lintStart free

What this skill tells your AI

The instructions your AI receives, as published by hashgraph-online/awesome-codex-plugins in plugins/mturac/env-lint/skills/env-lint/SKILL.md and read by ahel’s review.

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.

Signals

GitHub stars
1k
Forks
316
Last commit
Oct 2026
Advanced
Item type
skill
Key
env-lint
Source
github.com/hashgraph-online/awesome-codex-plugins