atmos-introspection
Atmos Introspection
Purpose
Atmos provides powerful introspection commands (describe and list) for querying the stack graph,
component configurations, dependencies, and change impact. AI agents operating in a terminal should
use these commands to understand the user's workspace instead of guessing at configurations.
When to Use Introspection
- Before generating configuration -- Run
atmos describe componentto see the current resolved config - To find dependencies -- Run
atmos describe dependentsto see what depends on a component - To understand project structure -- Run
atmos list stacksandatmos list components - For CI/CD -- Run
atmos describe affectedoratmos list affectedto detect changed stacks - To debug configuration -- Use
--provenanceto trace where values originate
Describe Commands
atmos describe component
More from cloudposse/atmos
atmos-design-patterns
Design patterns: stack organization, component catalogs, inheritance, configuration composition, version management, layered configuration
15atmos-config
Project configuration: atmos.yaml structure, all sections, discovery, merging, base paths, settings, imports, profiles
12atmos-workflows
Workflow automation: multi-step workflows, Go template support, cross-component orchestration
12atmos-helmfile
Helmfile orchestration: sync/apply/destroy/diff, Kubernetes deployments, varfile generation, EKS integration, source management
12atmos-stores
Store backends: AWS SSM, Azure Key Vault, Google Secret Manager, Redis, Artifactory configuration, hooks integration, cross-component data sharing
11atmos-stacks
Stack configuration: imports, inheritance, deep merging, locals, vars, settings, metadata, overrides
10