config-env

Discover and manage AICP environment variables and config overlays across the 5-tier load order.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/cyberpunk042/devops-expert-local-ai --skill config-env-cyberpunk042
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: config-env
Source: https://github.com/cyberpunk042/devops-expert-local-ai/tree/main/.claude/skills/config-env
Command: npx skills add https://github.com/cyberpunk042/devops-expert-local-ai --skill config-env-cyberpunk042

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing environment variables and per-environment configuration across multiple overlays is error-prone and tedious. This skill provides a unified surface to view, override, and validate environment settings for AICP, ensuring consistent behavior across dev, staging, and prod.

Core Features & Use Cases

  • Overlay-based config: base/default.yaml plus profile overlays plus user/project overrides to determine the final config.
  • Env-var mediation: read and override select keys via AICP_* vars, with clear documentation in .env.example.
  • Debugging and tracing: identify which tier supplied a value and reproduce per-environment configurations for tests, QA, and deployment.

Quick Start

Set a new environment variable for the current session and verify which config overlay is active for the run.

Frequently Asked Questions about config-env

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

FAQPage Schema
How do I manage environment variables across dev, staging, and prod configurations?

Manage environment variables across dev, staging, and prod by applying config overlays through a 5-tier load order. The system reads base defaults, profile settings, user configs, project configs, and CLI flags to determine final per-environment values.

What is the best way to debug which config overlay supplied a specific environment variable?

Debug config overlays by tracing the 5-tier load order to identify which layer supplied a value. The system provides loading behavior and traceability by reading env vars, applying overlays, and validating the final configuration for tests and QA.

How do I override default.yaml settings with project-level configuration files?

Override default.yaml settings by applying project-level configuration files in the load order. The system merges default.yaml, profile overlays, user configs, and project-level .aicp/config.yaml files to validate the final merged configuration.

Can I use AICP environment variables to override select configuration keys?

Yes, you can use AICP environment variables to mediate and override select configuration keys. The system reads these vars to apply overrides on top of the existing config overlays, ensuring consistent behavior across deployment environments.

Why does my final configuration not match the expected environment profile?

Final configurations may mismatch expected profiles due to the 5-tier load order precedence. The system resolves this by reading env vars, applying overlays from default.yaml to CLI flags, and validating the final configuration trace.

How do I set up per-environment configuration workflows for testing and deployment?

Set up per-environment workflows by defining profile overlays and project overrides within the load order. The system validates final configurations and provides traceability to reproduce dev, staging, and prod environments for tests and deployment.