config-structure-reviewer

Inventory configuration sources and separate build-time, deploy-time, and runtime settings.

Updated Apr 19, 2026

Search Tags:#security #validation #config #environment-variables #configuration-management #build-config #runtime-config

Ready to run

npx skills add https://github.com/saranskumar/anti-slop --skill config-structure-reviewer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: config-structure-reviewer
Source: https://github.com/saranskumar/anti-slop/tree/main/skills/config-structure-reviewer
Command: npx skills add https://github.com/saranskumar/anti-slop --skill config-structure-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews and clarifies how a codebase organizes configuration files, environment variables, runtime options, feature flags, and per-environment settings to prevent ambiguity and risk.

Core Features & Use Cases

Inventory config sources and consumers to improve traceability.
Separate build-time, deploy-time, and runtime configuration to reduce duplication and leakage risks.
Identify duplication, hidden defaults, and secret leakage risks; propose a clearer structure and validation path.

Quick Start

Identify config sources, separate runtime and build-time settings, and propose a clearer, validated structure.

Frequently Asked Questions about config-structure-reviewer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I separate build-time, deploy-time, and runtime configuration in my codebase?▼

To separate configuration, you must inventory all config sources and consumers to enforce boundaries between build-time, deploy-time, and runtime settings. This process reduces duplication and prevents secret leakage risks across your environments.

What is the best way to audit environment variables for secret leakage risks?▼

Auditing environment variables involves inventorying all config sources to identify hidden defaults, duplication, and potential secret leakage. This strict validation and auditing process ensures explicit, safe, and maintainable settings across your codebase.

Why should I review my codebase configuration management structure?▼

You should review configuration management to prevent ambiguity and risk caused by scattered environment variables and mixed runtime options. Organizing these sources makes configurations explicit, safe, and maintainable while improving overall traceability.

How do I inventory config sources and consumers to improve traceability?▼

Inventorying config sources requires identifying every environment variable, feature flag, and per-environment setting within your codebase. This strict auditing clarifies consumers, exposes hidden defaults, and proposes a clearer, validated structure.

Does this configuration review work for codebases with scattered environment variables?▼

Yes, this configuration review is designed specifically for codebases with scattered environment variables and mixed runtime, build, and deploy configurations. It flags strict validation paths to resolve ambiguity and prevent leakage risks effectively.

When do I need to enforce strict validation for environment variables?▼

You need strict validation for environment variables when your codebase has mixed runtime and build-time settings with hidden defaults. Enforcing validation prevents secret leakage, reduces duplication, and proposes a clearer, safer configuration structure.