Guide Terraform and OpenTofu workflows through fmt, validate, plan, and apply.
npx skills add https://github.com/ulf1/trading-regime --skill 340-terraform
Please help me install this Agent Skill. Skill: 340-terraform Source: https://github.com/ulf1/trading-regime/tree/main/.agent/skills/340-terraform Command: npx skills add https://github.com/ulf1/trading-regime --skill 340-terraform
This skill prevents risky infrastructure changes by guiding you through Terraform’s declarative workflow and state-safe practices, so you avoid plan drift, accidental replacements, and common HCL/provider pitfalls.
terraform import to bring existing infrastructure under Terraform management instead of recreating it.for_each key determinism, null vs empty strings, sensitive data handling, and provider version attribute changes.Use the 340-terraform skill to review your Terraform plan for potential force-replacements and tell you exactly what to change before you apply.
High-intent search queries and answers about installing and using this skill.
To safely plan and apply Terraform changes, follow a contract-first workflow using fmt, validate, plan, and apply in order. Reviewing plan symbols like +, -, and ~ helps minimize blast radius and prevent accidental replacements.
A Terraform plan shows force-replacements when attributes require destructive changes. Reviewing plan symbols like -/+ identifies affected resources, and adjusting HCL syntax or provider version attributes can prevent unnecessary replacements.
Import existing infrastructure into Terraform state using import blocks or the terraform import command. This brings existing cloud resources under Terraform management without recreating them, ensuring state and real-world infrastructure align.
The best way to structure Terraform environments is using an environment-per-directory layout without workspaces. Safe state management requires no manual .tfstate edits and no secrets hardcoding in HCL files.
Yes, OpenTofu uses the same HCL syntax and declarative workflow as Terraform. Applying safety practices like plan interpretation, state-security constraints, and fmt/validate/plan/apply ordering ensures safe OpenTofu infrastructure changes.
Common Terraform HCL gotchas include ensuring for_each key determinism, distinguishing null versus empty strings, and handling sensitive data properly to avoid hardcoding secrets. Provider version attribute changes can also trigger unexpected plan drift.
pantheon-orgValidate, lint, and security-scan Terraform configurations and HCL files.
enchantednaturesPlan and execute reversible database, code, and infrastructure migrations.
adrien-barretAnalyze Terraform configurations for structural, security, and operational issues.
partme-aiGuide Terraform infrastructure as code with HCL syntax and state management.