What problem does it solve? A program's configuration system — its sources, precedence order, defaults, and failure behavior — is rarely documented as a whole, so operators set values that silently lose to another source, rely on defaults nobody wrote down, or ship secrets through plumbing nobody traced. This Skill reconstructs that system from the code and reports it as verifiable findings. ## Core Features & Use Cases - Source and precedence reconstruction: Inventories config files, environment variables, CLI flags, profiles, and remote settings, then reads the loader to state exactly how they merge and which source wins. - Settings surface audit: Counts the configurable settings by area, cross-checks code against documentation, and flags undocumented settings the code reads and stale settings the docs promise but the code ignores. - Secrets plumbing and validation review: Traces how credentials travel from env vars, key files, keychains, or vaults into clients, and reports how bad or missing configuration is validated and handled at startup versus first use. - Use Case: Point it at a repository with a Sokrates analysis and ask how the application is configured; it produces a structured findings report (sources, precedence, defaults, feature flags, reload behavior) rendered into an interactive HTML explorer. ## Quick Start Ask the AI to run the configuration scan on this repository and report where each setting comes from, which source wins, and what happens when configuration is missing or invalid.
