ia-terraform

Enforce Terraform and OpenTofu configuration discipline with HCL structure, state safety, and verification workflows.

30|3|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/iliaal/whetstone --skill ia-terraform
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ia-terraform
Source: https://github.com/iliaal/whetstone/tree/main/plugins/whetstone/skills/ia-terraform
Command: npx skills add https://github.com/iliaal/whetstone --skill ia-terraform

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Terraform and OpenTofu outputs can look polished while skipping the engineering discipline needed for correctness, safety, and maintainability, especially across state changes and module refactors.

Core Features & Use Cases

  • Terraform/OpenTofu HCL structure and naming: Enforces consistent file organization, naming conventions, block ordering, and module layout so changes stay readable during reviews.
  • Safe, repeatable state and security practices: Guides remote backends, locking, state encryption, secret handling, and least-privilege security patterns to reduce outages and leaks.
  • Native testing and verification workflows: Uses terraform fmt/validate/tflint/trivy plus native terraform test and mock provider patterns to verify before claiming done.

Quick Start

Ask the agent to review your OpenTofu module for the staging environment and produce a corrected, testable HCL structure that follows the skill’s ordering, naming, state, security, and verification steps.

Frequently Asked Questions about ia-terraform

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce consistent Terraform module structure and block ordering during code review?

Terraform module structure is enforced by applying consistent file organization, naming conventions, and block ordering rules. This ensures HCL configurations remain readable and maintainable during OpenTofu infrastructure reviews.

What's the best way to secure Terraform state and prevent secret leaks in HCL configurations?

Securing Terraform state involves configuring remote backends with locking, enabling state encryption, and following secret-free handling patterns. These practices reduce the risk of outages and sensitive data leaks across infrastructure changes.

How do I add native tests to verify Terraform configurations before applying changes?

Native Terraform tests verify configurations by running fmt, validate, tflint, and trivy security scanning alongside mock provider patterns. These verification gates confirm HCL correctness before infrastructure changes are merged.

Can I use this approach to review both Terraform and OpenTofu workflows?

Both Terraform and OpenTofu configurations are supported for review and correction. The skill applies disciplined practices for HCL writing, state migration patterns, and security controls across both infrastructure as code platforms.

Why does my Terraform configuration pass validation but still fail during state migration?

Terraform validation checks syntax but does not verify safe state migration patterns or backend configurations. Disciplined reviews catch fragile state changes, missing locking, and unsafe refactors that basic validation skips.

What file organization and naming conventions should I follow for Terraform modules?

Terraform modules require consistent file organization, standardized naming conventions, and correct block ordering to maintain readability. Following these patterns ensures changes are verifiable and safe during infrastructure code reviews.