devtools
Env Example Generator
Scan your repo, detect every process.env.*, and publish a complete .env.example in minutes.
Most contributor setup failures happen because environment variables are missing or undocumented. This tool reads your codebase, finds every referenced key, and writes a practical .env.example with AI-generated descriptions so new contributors can run your project without guesswork.
What maintainers fix first
Faster first contribution flow, fewer setup questions, and cleaner issue triage.
Catch stale keys before release and avoid broken README setup docs.
Generate consistent variable descriptions for internal and external contributors.
Support public and private repos through GitHub OAuth permissions.
1) Connect or paste URL
owner/repo for public repos or connect GitHub to scan private code.2) Scan all env usages
process.env references.3) Generate and copy
.env.example ready for commit.Simple pricing for maintainers and small teams
This is a niche DX tool with a tiny wedge price: cheap enough for solo maintainers, predictable for teams running many repos.
- $2 one-time personal license
- $7/mo team license
- Unlimited scans and generation
FAQ
Will it work on private repositories?
Yes. Connect GitHub with OAuth, and the scanner will use your token to read private files with your existing repo permissions.
How accurate are environment variable descriptions?
Descriptions combine static code context and OpenAI analysis. You can still edit wording before committing the generated file.
Do you store my repository code?
No full clone is persisted. Files are streamed for scanning and only variable metadata is returned to your session.
Can I use it for monorepos?
Yes. The scanner walks the repository tree and finds env usage across packages and services.