Review Terraform or OpenTofu plan JSON for destructive changes, replacement order, state and provider risk, unknown values, rollout gates, and recovery requirements before apply.
A Terraform plan can be syntactically valid and still be unsafe to apply. Targeting can hide dependencies. A create-before-destroy replacement can fail on quota or naming. A zero-change plan after an interrupted apply can say nothing useful about runtime health. A state backup does not recreate deleted infrastructure or data.
Terraform Plan Review binds the exact plan to its configuration, dependency lockfile, workspace, backend, state lineage and serial, command flags, variable sources, and freshness before judging the diff. It inventories creates, updates, deletes, replacement order, sensitive paths, unknown values, output changes, state moves, imports, provider behavior, and evidence gaps. It then reviews data, identity, network, availability, quota, cost, observability, ownership, and recovery boundaries in consequence order.
The package includes a local Python parser for complete terraform show -json output. The parser produces a deterministic resource/action inventory, replacement paths, action reasons, sensitive paths, unknown paths, output changes, and structural attention flags. It never prints sensitive values or declares a plan safe. The review workflow adds a risk rubric, gate matrix, staged apply design, rollback-versus-recovery test, four bounded verdicts, and a handoff template. It does not run Terraform or OpenTofu, mutate state, break locks, approve, or apply infrastructure.
Version 1.0.0 was reviewed on 2026-07-24 and evaluated through Codex CLI with gpt-5.6-sol in 12 fresh read-only contexts. Across three cases, the candidate scored 100, compared with 85.83 for the same agent without the skill and 90.83 for the exact free upstream. It passed all three cases and led the upstream by 9.17 points overall. The evaluation covers the supplied database-replacement, interrupted-apply, and network-cutover cases. It does not prove a real plan is complete, a provider will behave as expected, recovery will work, or any infrastructure is safe to apply.
The reviewed package SHA-256 is 8141138a9cf30c17e2df30c4f982acff0aa5001405864cccbfa5ed63e9a7aaa8. Maintenance and install support are handled by the platform-operated publisher for this listing.
Input
The plan uses `-target` and `-replace`, deletes then recreates the primary database, changes a security group, and leaves endpoint values unknown. State identity, downstream dependencies, and tested restore evidence are missing.
Output
A bound evidence record; explicit delete-before-create and security-change inventory; targeted-scope limitation; data, access, outage, consumer, and recovery gates; a blocked verdict; and one action to produce a fresh complete plan and tested recovery evidence.
Input
An apply lost its final exit status after a provider timeout. A later `-refresh=false` plan shows zero changes, the configuration and lockfile changed, the state lock and provider outcome are unknown, and service health is degraded.
Provide a saved Terraform/OpenTofu plan rendered as JSON, the exact plan command and flags, tool version, configuration commit and working-tree state, lockfile and provider selections, workspace, backend, state lineage and serial, variable sources, environment criticality, runtime baseline, and separate review, command, state, approval, apply, and recovery authority. Ask for a plan review before apply or for post-apply recovery review after an interrupted operation. The skill keeps missing evidence explicit and never treats plan structure as approval.
A complete `terraform show -json` or `tofu show -json` export is preferred. Include its path, byte size, SHA-256, creation time, and tool version. Text plans and pasted excerpts remain partial evidence.
Immutable configuration commit, declared working-tree state, dependency lockfile hash, provider versions and checksums, module revisions, exact plan command, flags, and variable sources.
Workspace, backend and key, state lineage and serial, latest state event, environment criticality, current runtime health, maintenance window, and any plan or apply activity after artifact creation.
Separate review, command-execution, state, approval, apply, and recovery authority plus named planner, reviewer, approver, apply operator, observability owner, and recovery owner.
SKILL.md; Terraform/OpenTofu plan JSON summarizer; plan-risk and gate rubric; review, staged rollout, recovery, and handoff template
No reviews yet.
Output
An evidence hold; contradictions; read-only process, state, provider, and runtime reconciliation branches; prohibited retry and lock-breaking actions; a post-apply-recovery-review verdict; and one evidence-preserving next action.
Input
A bound plan creates a new load balancer and IAM role, updates DNS and monitoring, then deletes the old load balancer. DNS, listener, role, and monitoring identifiers are unknown until apply, while quota and runtime validation are stale or missing.
Output
A cross-resource blast-radius review; decision-sensitive unknown-value map; current quota, certificate, IAM, target-health, DNS, monitoring, cost, ownership, and approval gates; staged cutover and recovery design; and a needs-evidence verdict.
Creator
Ggalvio9
