ahmedasmar/iac-terraform
Infrastructure as Code with Terraform and Terragrunt. Use this skill whenever the user mentions Terraform, Terragrunt, HCL, or infrastructure as code. Triggers include writing or reviewing .tf files, creating reusable modules, debugging terraform plan/apply errors, managing remote state and locks, fixing state drift, setting up CI/CD for Terraform, scaffolding new modules, validating module structure, and implementing Terragrunt DRY patterns across environments.
npx skills add https://github.com/ahmedasmar/devops-claude-skills --skill iac-terraform
Comprehensive guidance for infrastructure as code using Terraform and Terragrunt, from development through production deployment.
Workflow Decision Tree:
Is this reusable across environments/projects?
├─ Yes → Create a Terraform module
│ └─ See "Creating Terraform Modules" below
└─ No → Create environment-specific configuration
└─ See "Environment Configuration" below
When building reusable infrastructure:
python3 scripts/init_module.py my-module-name
This automatically creates:
assets/templates/MODULE_TEMPLATE.md for complete structuremain.tf, variables.tf, outputs.tf, versions.tf, README.mdexamples/ directory with working examplesvalidation blockssensitive = truepython3 scripts/validate_module.py /path/to/module
This checks for:
cd examples/complete
terraform init
terraform plan
terraform-docs markdown . > README.mdKey Module Patterns:
See references/best_practices.md "Module Design" section for:
For environment-specific infrastructure:
environments/
├── dev/
├── staging/
└── prod/
environment/
├── main.tf # Resource definitions
├── variables.tf # Variable declarations
├── terraform.tfvars # Default values (committed)
├── secrets.auto.tfvars # Sensitive values (.gitignore)
├── backend.tf # State configuration
├── outputs.tf # Output values
└── versions.tf # Version constraints
module "vpc" {
source = "git::https://github.com/company/terraform-modules.git//vpc?ref=v1.2.0"
name = "${var.environment}-vpc"
vpc_cidr = var.vpc_cidr
environment = var.environment
}
When to inspect state:
Inspect state and check health:
# List all managed resources
terraform state list
# Show detailed state for a specific resource
terraform state show <resource_address>
# Show full state summary (all resources, outputs, providers)
terraform show
Check for drift:
# Exit code 0 = no changes, 1 = error, 2 = drift detected
terraform plan -detailed-exitcode
State operations:
# List all resources
terraform state list
# Show specific resource
terraform state show aws_instance.web
# Remove from state (doesn't destroy)
terraform state rm aws_instance.web
# Move/rename resource
terraform state mv aws_instance.web aws_instance.web_server
# Import existing resource
terraform import aws_instance.web i-1234567890abcdef0
State best practices: See references/best_practices.md "State Management" section for:
# 1. Initialize (first time or after module changes)
terraform init
# 2. Format code
terraform fmt -recursive
# 3. Validate syntax
terraform validate
# 4. Plan changes (always review!)
terraform plan -out=tfplan
# 5. Apply changes
terraform apply tfplan
# 6. Verify outputs
terraform output
With Terragrunt:
# Run for single module
terragrunt plan
terragrunt apply
# Run for all modules in directory tree
terragrunt run-all plan
terragrunt run-all apply
When encountering errors:
references/troubleshooting.md which covers:export TF_LOG=DEBUG
export TF_LOG_PATH=terraform-debug.log
terraform plan
# Test specific resource
terraform plan -target=aws_instance.web
terraform apply -target=aws_instance.web
State locked (full resolution guide: references/troubleshooting.md → State Lock Error):
# Verify no one else running, then:
terraform force-unlock <lock-id>
Provider cache issues:
rm -rf .terraform
terraform init -upgrade
Module cache issues:
rm -rf .terraform/modules
terraform init
Before committing:
terraform fmt -recursive
terraform validate
tflint --module
checkov -d .
python3 scripts/validate_module.py modules/vpc
terraform-docs markdown modules/vpc > modules/vpc/README.md
Review checklist:
See references/best_practices.md for comprehensive guidelines.
terragrunt-project/
├── terragrunt.hcl # Root config
├── account.hcl # Account-level vars
├── region.hcl # Region-level vars
└── environments/
├── dev/
│ ├── env.hcl # Environment vars
│ └── us-east-1/
│ ├── vpc/
│ │ └── terragrunt.hcl
│ └── eks/
│ └── terragrunt.hcl
└── prod/
└── us-east-1/
├── vpc/
└── eks/
# In eks/terragrunt.hcl
dependency "vpc" {
config_path = "../vpc"
# Mock outputs for plan/validate
mock_outputs = {
vpc_id = "vpc-mock"
subnet_ids = ["subnet-mock"]
}
mock_outputs_allowed_terraform_commands = ["validate", "plan"]
}
inputs = {
vpc_id = dependency.vpc.outputs.vpc_id
subnet_ids = dependency.vpc.outputs.private_subnet_ids
}
See assets/templates/MODULE_TEMPLATE.md for complete Terragrunt configuration templates including:
references/best_practices.md — Project structure, state management, module design, security, CI/CD integrationreferences/troubleshooting.md — State lock errors, drift, provider issues, resource errors, Terragrunt-specific problemsreferences/cost_optimization.md — Right-sizing, Spot/RI strategies, storage optimization, cost tagging, multi-cloudReady-to-use templates in assets/workflows/:
| Template | Platform | Features |
|----------|----------|----------|
| github-actions-terraform.yml | GitHub Actions | Validation, TFLint, Checkov, plan on PRs, apply on main, OIDC |
| github-actions-terragrunt.yml | GitHub Actions | Changed module detection, parallel planning, dependency-aware apply |
| gitlab-ci-terraform.yml | GitLab CI | Multi-stage pipeline, artifact management, manual gates |
| Script | Purpose | Usage |
|--------|---------|-------|
| init_module.py | Scaffold new module with standard structure | python3 scripts/init_module.py <name> [--path ./modules] [--json] |
| validate_module.py | Validate module against best practices | python3 scripts/validate_module.py <path> |
templates/MODULE_TEMPLATE.md — Complete module template with file structure, examples, and Terragrunt configs# Initialize
terraform init
terraform init -upgrade # Update providers
# Validate
terraform validate
terraform fmt -recursive
# Plan
terraform plan
terraform plan -out=tfplan
# Apply
terraform apply
terraform apply tfplan
terraform apply -auto-approve # CI/CD only
# State
terraform state list
terraform state show <resource>
terraform state rm <resource>
terraform state mv <old> <new>
# Import
terraform import <resource_address> <resource_id>
# Destroy
terraform destroy
terraform destroy -target=<resource>
# Outputs
terraform output
terraform output <output_name>
# Single module
terragrunt init
terragrunt plan
terragrunt apply
# All modules
terragrunt run-all plan
terragrunt run-all apply
terragrunt run-all destroy
# With specific modules
terragrunt run-all apply --terragrunt-include-dir vpc --terragrunt-include-dir eks
Take ahmedasmar/iac-terraform from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.