Analyze Terraform plans for risk before you apply. Classifies every change as safe, moderate, dangerous, or critical. Detects destroys, IAM changes, data-loss risks, and blast radius. Entirely read-only — never runs apply.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
Analyze Terraform plans for risk before you apply. Classifies every change as safe, moderate, dangerous, or critical. Detects destroys, IAM changes, data-loss risks, and blast radius. Entirely read-only — never runs apply.
Analyze terraform plan output and produce an AI-powered risk assessment of every infrastructure change — before you press apply.
This skill is STRICTLY READ-ONLY. It runs terraform plan and terraform validate to analyze changes, but it NEVER runs terraform apply, terraform destroy, terraform import, terraform taint, or any command that modifies infrastructure or state.
"IAM changes", "security group changes", "infrastructure changes"
"blast radius", "cascade effects", "dependencies"
"tofu plan", "opentofu" (same workflow, different binary)
Example Prompts
"Review this terraform plan before I apply"
"What will be destroyed in this plan?"
"Is this plan safe to apply?"
"Show me the state drift"
"What IAM changes are in this plan?"
"Validate my terraform config in ~/infra/prod"
"Run a risk assessment on the terraform plan in /deployments/staging"
"What's the blast radius if I apply this plan?"
Permissions
permissions:exec:true# Required to run terraform/tofu CLIread:true# Read .tf files and plan outputwrite:false# NEVER writes — strictly read-only analysisnetwork:true# terraform plan needs provider API access
Terraform Change Types — What the Agent Must Know
Understanding Terraform change types is critical for accurate risk assessment:
Action Types (from plan JSON)
Action
Meaning
Risk Profile
create
New resource being added
Generally safe (unless IAM/security)
update
Existing resource modified in-place
Moderate (depends on what's changing)
delete
Resource being permanently destroyed
DANGEROUS — data loss risk
replace (delete + create)
Resource must be destroyed and recreated
DANGEROUS — downtime + data loss
read
Data source being refreshed
Safe (read-only)
no-op
No changes needed
Safe
What Makes a Change Dangerous
Critical (🔴 CRITICAL):
Any destroy/replace of: IAM roles/policies, security groups, KMS keys, secrets, databases (RDS, DynamoDB, Cloud SQL, Azure SQL), S3 buckets, DNS records, WAF rules, CloudTrail
Any update to IAM policies, security group rules, encryption settings
These changes can cause data loss, security breaches, or service outages
These changes cause downtime and may require manual intervention to recover
Moderate (🟡 MODERATE):
Updates to: autoscaling policies, monitoring/alerting rules, launch templates
Creates of: security-sensitive resources (new IAM roles, new security groups)
Changes that affect capacity or observability but not data integrity
Safe (🟢 SAFE):
Tag-only updates
Creating new non-sensitive resources
No-op / read operations
Replace is Especially Dangerous
When Terraform says it must "replace" a resource, it means:
Delete the existing resource (irreversible)
Create a new one with the new configuration
This is triggered when an immutable attribute changes (e.g., changing RDS engine_version, EC2 ami, changing a subnet's AZ). The agent should always flag replaces prominently because:
The old resource (and its data) is destroyed
There will be a gap between destroy and create (downtime)
Dependent resources may break during the transition
Agent Workflow
Follow this sequence exactly based on user intent:
For Plan Analysis ("review this plan", "is it safe", "what changes")
Step 1: Run Plan Analysis
bash <skill_dir>/scripts/tf-plan-review.sh plan <directory>
If no directory specified, use the current working directory.
The script outputs:
stdout: Structured JSON with all resource changes, risk classifications, and summary
Extracts error from plan JSON diagnostics, reports it
Plan timeout
Process killed after TF_PLAN_TIMEOUT seconds
State not found
JSON error explaining no state exists
Empty state
Reports "State is empty — no managed resources"
Safety — CRITICAL RULES
NEVER run terraform apply — not even with -auto-approve, not even with -target, not even "just this one resource". NEVER.
NEVER run terraform destroy — not under any circumstances.
NEVER run terraform import — this modifies state.
NEVER run terraform taint or terraform untaint — these modify state.
NEVER run terraform state mv, terraform state rm, or terraform state push — these modify state.
Never expose cloud credentials — if they appear in plan output, redact them.
Handle sensitive values — Terraform marks values as (sensitive). Never try to reveal them.
Never cache or store plan output — plans can contain secrets in resource attributes.
The ONLY terraform commands this skill runs are: plan, show, state list, state show, validate, init, providers.
If the user asks you to apply a plan, respond:
"I can analyze and assess Terraform plans, but I cannot apply them. Applying infrastructure changes requires human review and explicit execution. Based on my analysis, here's what you should verify before running terraform apply..."
Common Patterns & Agent Tips
"Is this plan safe to apply?"
Run the plan analysis. If overall_risk is 🟢 LOW:
"This plan looks safe. It creates X new resources with no destroys or security changes. The pre-apply checklist is straightforward."
If overall_risk is 🔴 CRITICAL:
"⚠️ This plan has CRITICAL risk. [Explain specific dangers]. I strongly recommend review by another team member before applying."
"What will be destroyed?"
Run plan, then filter for action == "delete" or action == "replace". Present each with:
Resource address
Resource type
Why it matters (is it stateful? does it have data?)
What depends on it
"What IAM changes are in this plan?"
Run plan, then filter resources matching IAM patterns. For each:
What permission is changing
Is it adding or removing access
Is it overly permissive (e.g., Action: *)
"Show me the blast radius"
Run plan, identify all destroys/replaces, then explain:
What other resources reference the destroyed ones
What will break when the resource is gone
Whether Terraform will auto-fix the dependencies or if manual intervention is needed
Discord v2 Delivery Mode (OpenClaw v2026.2.14+)
When the conversation is happening in a Discord channel:
Send a compact first summary (overall risk, destroy count, critical resources), then ask if the user wants the full report.
Keep the first response under ~1200 characters and avoid large Markdown tables in the first message.
If Discord components are available, include quick actions:
Show Critical Changes
Show Destroyed Resources
Show Pre-Apply Checklist
If components are not available, provide the same follow-ups as a numbered list.
Prefer short follow-up chunks (<=15 lines per message) for large plans.
Sensitive Data Handling
Terraform plan JSON may contain sensitive values. The script does NOT extract resource attribute values — it only extracts resource addresses, types, and actions. However, when presenting results:
Never show attribute values marked (sensitive) by Terraform
Never show provider credentials or backend configuration secrets
If a user asks "what value is changing?", explain that you can see the change type but sensitive values are redacted by Terraform for security
