autonomy--env-auditor

Audit environment variable loading readiness by inventorying env var references across code and config, evaluating loading mechanisms and secret sources, then performing a cold-start test to identify blockers and document remediation steps.

Agent setup fails loading .env variables from scratch when the repository lacks proper loading mechanisms or secret source documentation. Run an env-loading assessment to discover missing references, identify blockers, and generate required remediation steps.

A cold-start environment loading assessment evaluates whether a repository can load all required environment variables without pre-existing .env files, inventorying references and recording blockers to ensure AI agent readiness during onboarding harness checks.

You should not use an env-loading readiness audit when .env files already load correctly and the goal is adding a single new variable, or when creating env loading capability, which requires a different env-creator approach instead.

Yes, you can check secret sources and dotenv configuration readiness by evaluating the environment loading mechanism and documenting whether all required variables can load from a cold start, recording any blockers found during the harness assessment.

The best way to document environment setup blockers is running a cold-start env-loading assessment that inventories variable references, evaluates loading mechanisms, and records all blockers with explicit remediation steps in an audit report.