mertjane

Env Audit — Security skill for Claude Code

Security community

Compares .env against .env.example (or .env.sample, .env.template) and reports missing variables, undocumented extras, and security risks such as hardcoded secrets or weak values.

How to install Env Audit

Installs to ~/.claude/skills/mertjane-awesome-claude-commands-env-audit/SKILL.md

Terminal

mkdir -p ~/.claude/skills/mertjane-awesome-claude-commands-env-audit && curl -fsSL https://raw.githubusercontent.com/mertjane/awesome-claude-commands/HEAD/commands/env-audit.md -o ~/.claude/skills/mertjane-awesome-claude-commands-env-audit/SKILL.md

Restart Claude Code, or start a new session, for it to be picked up.

What Env Audit does

description: Compares .env against .env.example (or .env.sample, .env.template) and reports missing variables, undocumented extras, and security risks such as hardcoded secrets or weak values. argument-hint: [env-file] allowed-tools: [Read, Glob]

Environment Variables Audit

Audit the project's environment variable files and produce a report covering missing variables, undocumented extras, and security risks.

If $ARGUMENTS is provided, use it as the path to the active env file. Other

Alternatives in Security

Security Ownership Map — Map people-to-file ownership, compute bus factor, and identify risks 14.6k ★
Compat Audit — On-demand Claude Code compatibility and feature parity report — compares installed version against the breakpo 117 ★
Audit Patterns — Design patterns audit 63 ★