kit-terraform
Write, change, or review Terraform or OpenTofu configuration following the repository's module layout and conventions, with pinned providers, safe defaults for security and state, and verification by
SKILL.mdregistry/skills/terraform/SKILL.md
GitHubTerraform
Run only terraform fmt, terraform init -backend=false (with -lockfile=readonly when reviewing), terraform validate, and terraform plan with the user's consent. Never run anything else that touches state or remote systems, such as apply, destroy, import, refresh, state or workspace changes, taint, untaint, force-unlock, or init -migrate-state. Applying is a deployment and needs the user's explicit instruction; leave it to them.
1. Learn the layout
- Find root modules and environments (directories, workspaces, or Terragrunt), shared modules, the backend and state configuration, provider and Terraform version constraints, variable conventions, and tagging or naming standards. Follow them.
- Read the resources around the change and any module the change should reuse instead of duplicating.
2. Write or review
- Pin
required_versionand providers with~>constraints, and commit.terraform.lock.hclin root modules (shared modules do not use one). - Use variables with types, descriptions, and
validationblocks for inputs; mark secretssensitive = trueand never hard-code credentials or secret values. - Security defaults: storage not public (block public access on buckets), encryption at rest, least-privilege IAM (no
*actions or resources without a stated reason), security groups without0.0.0.0/0on admin ports, logging enabled where the platform supports it. - Protect stateful resources with provider-side deletion protection and
prevent_destroywhere losing them would be costly;prevent_destroydoes not help once the resource block is removed. Watch for changes that force replacement (renames, changed immutable arguments) and usemovedblocks when refactoring addresses. - Use
for_eachovercountfor collections keyed by name, so removing one item does not shift the others.
3. Verify
Run terraform fmt -check (or fmt), terraform validate, and the project's linters (tflint, checkov, tfsec) if configured. Run terraform plan only when credentials and a non-production backend or environment are available and the user agrees; read the plan for replacements and deletions.
4. Report
Summarize resources added, changed, and destroyed or replaced, security-relevant choices, verification results, and the exact plan and apply steps for the user.
Examples
- Use: "Add an S3 bucket for uploads with encryption." "Review modules/network for security problems." "Why does this plan want to replace the database?"
- Skip: "Write a Helm chart." (kit-kubernetes) "Run terraform apply in prod."