Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
What This Skill Does
Scans a codebase for all referenced environment variables across JavaScript, TypeScript, Python, Go, Rust, and Docker files. Generates a .env.example with categorized placeholders, validates an existing .env against discovered variables, and checks .gitignore for secret safety.
Replaces manual grep sessions and guesswork by scanning all common env patterns across multiple languages in one pass and cross-referencing them against your actual .env.
When to use it
- Finding missing env vars before a deployment fails
- Onboarding a new developer with a complete .env.example
- Auditing which secrets are exposed in git history
- Cleaning up stale variables left in .env after refactoring
- Verifying .gitignore protects all environment files
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: scan my project and generate a .env.example
- 1Grep codebase across .js, .ts, .py, .go, .rs, and docker-compose files for env var references
- 2Extract and deduplicate variable names, noting source file and line number for each
- 3Classify variables into secrets, service URLs, and configuration groups
- 4Generate .env.example with placeholder values and category comment headers
- 5Check .gitignore for .env entries and scan git history for accidentally committed env files
A .env.example file with 15 categorized variables, a validation report showing 2 missing and 1 unused variable in the current .env, and a .gitignore safety confirmation