Scan code for getenv calls and flag undocumented environment variables.
npx skills add https://github.com/CaptainPhantasy/floyd-v5 --skill env-validate
Please help me install this Agent Skill. Skill: env-validate Source: https://github.com/CaptainPhantasy/floyd-v5/tree/main/extensibility/skills/dx/env-validate Command: npx skills add https://github.com/CaptainPhantasy/floyd-v5 --skill env-validate
Scans code to find environment variable usages and verifies they are documented in the env file (.env.example), reducing configuration drift and runtime errors.
Run the env-validate tool on your repository to verify that all environment variables used in code are declared in .env.example and report any discrepancies.
High-intent search queries and answers about installing and using this skill.
To validate environment variables against .env.example, you can scan your codebase to detect getenv calls and map them to central .env.example entries to flag undocumented variables.
Environment variable validation identifies all environment variable usages in a codebase and ensures they are documented in the .env.example, reducing configuration drift and runtime errors during static analysis.
Yes, static analysis can scan large projects to detect getenv usage across the codebase and automatically flag undocumented variables to maintain consistent environment expectations.
Dotenv validation applies to languages and frameworks that access environment variables, performing code scans and documentation audits to ensure every variable used in code is represented.
The best way to prevent configuration drift is to run a validation tool on your repository to verify all environment variables used in code are declared in .env.example and report discrepancies.
You should perform an environment documentation audit during onboarding checks or when maintaining large projects to ensure every getenv call has a corresponding .env.example entry and avoid runtime errors.
rohanbhatia27Enhances code graphs with SARIF audit findings mapped to nodes by file and line overlap.
miles990Analyze git changes and propose commit messages and next actions.
prof-danielcRun static analysis tools and aggregate results into a prioritized issue report.
tikazyqGenerate multi-environment configuration checklists and .env.example templates.
