Communityv1.0.03 scenarios
Terragrunt
Community-authored Terragrunt guidance for include hierarchy drift, dependency output coupling, and run-all blast radius review.
deploywhisper skill install terragrunt
How to use this skill
1. Install it locally
Use the install command above from any DeployWhisper app checkout that has the installer enabled.
2. Run analysis on matching artifacts
This skill activates when files or content patterns below are detected during analysis.
3. Verify behavior
Published registry data currently includes 3 deterministic scenarios for this skill.
Metadata
Author
Infrastructure Guild Community
Version
1.0.0
License
MIT
Scenarios
3
Tags
Triggers
- terragrunt.hcl
Content patterns
- No content pattern hints declared.
Guidance excerpt
Critical risk patterns
- `run-all apply` or root include changes can fan out across many stacks at once = HIGH
- Dependency output contract changes can break downstream stacks even when the local diff looks small = HIGH
- Backend, remote state, or generate block changes can orphan state or rewrite provider configuration = CRITICAL
- Deep include hierarchy overrides can silently change locals, inputs, or hooks for every child module = HIGH
Review cues
- Review parent includes, dependency blocks, and generated provider files together before approving Terragrunt changes.
- Prefer stack-by-stack blast-radius notes over generic Terraform advice when the change alters shared Terragrunt scaffolding.