super-review:terraform

To detect Terraform anti-patterns in a pull request, review PR diffs modifying .tf or .tfvars files for risks like leaked secrets, lost state, and broken apply workflows using evidence-led checks. This surfaces issues automated linters often miss.

State-file safety in Terraform prevents committed or mismanaged state artifacts from leaking secrets or corrupting environments. It ensures backend state configurations remain secure during infrastructure changes, avoiding costly and irreversible infrastructure mistakes.

Yes, you can review OpenTofu and Terragrunt configurations for IAM policy discipline. Reviews target sensitive output handling, provider version pinning, and IAM authoring to ensure security and correctness across your IaC tooling.

The best way to prevent Terraform destroy risks and workflow drift is applying change-management guardrails. Detect missing backend locking, unsafe destroy risks, and enforce apply-from-plan discipline alongside lifecycle prevent_destroy protections.

Yes, PR-diff scoped review works with CDKTF directories, Terragrunt configurations, and standard Terraform files. It supplies actionable checklist items only when the diff indicates infrastructure as code is affected, focusing on count vs for_each stability.