credentials template generator

The problem

Developers often forget to update .env.example files as projects grow, leading to broken onboarding experiences for new teammates. Manually hunting through source code for process.env or os.getenv calls is tedious and prone to missing critical configuration requirements.

What it does

• Scans source code across multiple languages (Node.js, Python, Ruby, Java, PHP) to identify environment variable references.
• Extracts required keys from existing config files, docker-compose.yml, and CI/CD workflows.
• Categorizes variables into logical groups like Database, Auth, External Services, and App Settings.
• Generates formatted .env.example or .json.template files with safe placeholders.
• Cross-references README and CONTRIBUTING docs to capture documented but unlinked variables.

Frameworks & tools

Supports Node.js, Python, Ruby, Java, PHP, Docker, GitHub Actions, and GitLab CI. Works with .env, JSON, and YAML configuration formats.

Why this beats prompting it yourself

This skill follows a systematic multi-step analysis of your entire codebase rather than just guessing based on file names. It ensures consistency by categorizing variables and adding usage hints, preventing the "it works on my machine" syndrome during team onboarding.

Use cases

• Generating a .env.example for a legacy project that lacks documentation.
• Preparing a repository for public release or open-source contribution.
• Standardizing environment variable docs across microservices.
• Updating CI/CD secrets documentation after adding a new third-party integration.

Known limitations

Cannot detect variables that are dynamically constructed via string interpolation or fetched from external secret managers at runtime. Users must verify .gitignore settings manually.