Master Terraform state management including remote backends, locking, workspaces, and state operations
Manages Terraform state operations including remote backends, locking, and resource manipulation. Use when configuring S3/Azure/GCP backends, resolving state lock errors, importing existing resources, or moving/removing resources from state.
/plugin marketplace add pluginagentmarketplace/custom-plugin-terraform/plugin install terraform-assistant@pluginagentmarketplace-terraformThis skill inherits all available tools. When active, it can use any tool Claude has access to.
assets/config.yamlassets/schema.jsonreferences/GUIDE.mdreferences/PATTERNS.mdscripts/validate.pyComprehensive guide to state management, remote backends, and state manipulation operations.
terraform {
backend "s3" {
bucket = "company-terraform-state"
key = "prod/terraform.tfstate"
region = "us-east-1"
encrypt = true
dynamodb_table = "terraform-locks"
# Cross-account access
role_arn = "arn:aws:iam::ACCOUNT:role/TerraformAccess"
}
}
terraform {
backend "azurerm" {
resource_group_name = "terraform-state-rg"
storage_account_name = "tfstatecompany"
container_name = "tfstate"
key = "prod.terraform.tfstate"
use_azuread_auth = true
}
}
terraform {
backend "gcs" {
bucket = "company-terraform-state"
prefix = "terraform/state"
}
}
terraform {
cloud {
organization = "my-org"
workspaces {
tags = ["app:my-app", "env:prod"]
}
}
}
resource "aws_dynamodb_table" "terraform_locks" {
name = "terraform-locks"
billing_mode = "PAY_PER_REQUEST"
hash_key = "LockID"
attribute {
name = "LockID"
type = "S"
}
tags = {
Purpose = "Terraform state locking"
}
}
infrastructure/
├── environments/
│ ├── dev/
│ │ ├── main.tf
│ │ ├── backend.tf
│ │ └── terraform.tfvars
│ ├── staging/
│ └── prod/
└── modules/
# Create and switch
terraform workspace new prod
terraform workspace select prod
terraform workspace list
# Use in config
locals {
env_config = {
dev = { instance_type = "t3.micro" }
prod = { instance_type = "t3.large" }
}
config = local.env_config[terraform.workspace]
}
# Basic import
terraform import aws_instance.web i-1234567890
# Import into module
terraform import module.vpc.aws_vpc.main vpc-abc123
# Import with for_each
terraform import 'aws_instance.web["app-1"]' i-1234567890
# Generate config (Terraform 1.5+)
terraform plan -generate-config-out=generated.tf
# Rename resource
terraform state mv aws_instance.old aws_instance.new
# Move to module
terraform state mv aws_instance.web module.compute.aws_instance.web
# Move between states
terraform state mv -state-out=other.tfstate aws_instance.web aws_instance.web
# Remove without destroying
terraform state rm aws_instance.legacy
# Remove entire module
terraform state rm module.deprecated
# List resources
terraform state list
# Show resource details
terraform state show aws_instance.web
# Pull remote state
terraform state pull > state.json
# Push state (DANGEROUS)
terraform state push state.json
# Refresh and show drift
terraform apply -refresh-only
# Detailed plan with refresh
terraform plan -refresh=true
# Check for changes only
terraform plan -detailed-exitcode
# Exit codes: 0=no changes, 1=error, 2=changes
# Force unlock (only if confirmed stale!)
terraform force-unlock LOCK_ID
# Check DynamoDB for lock
aws dynamodb get-item \
--table-name terraform-locks \
--key '{"LockID":{"S":"path/to/state"}}'
| Error | Cause | Solution |
|---|---|---|
Error acquiring lock | Stale lock | Wait or force-unlock |
Backend config changed | Config modified | terraform init -reconfigure |
State out of sync | Manual changes | terraform apply -refresh-only |
Resource already exists | Import needed | terraform import |
# Backup current state
terraform state pull > backup.json
# Verify backup
cat backup.json | jq '.resources | length'
# Restore if needed
terraform state push backup.json
Skill("terraform-state")
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.