terraform-style-check

Enforce HashiCorp style conventions on Terraform HCL code.

820|64|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/warpdotdev/oz-skills --skill terraform-style-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: terraform-style-check
Source: https://github.com/warpdotdev/oz-skills/tree/main/.agents/skills/terraform-style-check
Command: npx skills add https://github.com/warpdotdev/oz-skills --skill terraform-style-check

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps ensure your Terraform HCL code adheres to HashiCorp's official style conventions and best practices, leading to more readable, maintainable, and consistent infrastructure as code.

Core Features & Use Cases

  • Style Enforcement: Provides guidelines for code formatting, file organization, naming conventions, and variable/output declarations.
  • Best Practice Guidance: Offers recommendations on dynamic resource creation, security, and version pinning.
  • Use Case: When writing new Terraform modules or reviewing existing configurations, use this Skill to verify adherence to established standards and identify potential areas for improvement.

Quick Start

Use the terraform-style-check skill to review the attached Terraform configuration file for style compliance.

Frequently Asked Questions about terraform-style-check

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

FAQPage Schema
How do I enforce Terraform HCL style conventions during code review?

To enforce Terraform HCL style conventions, apply guidelines for code formatting, file organization, naming conventions, and variable declarations. This ensures infrastructure as code remains readable, maintainable, and consistent with HashiCorp's official best practices.

What are HashiCorp's best practices for Terraform code formatting and organization?

HashiCorp's Terraform best practices include specific standards for code formatting, file organization, naming conventions, and variable/output declarations. Adhering to these guidelines improves readability and consistency across infrastructure configurations.

Can I check my existing Terraform configurations for style compliance?

Yes, you can review existing Terraform configurations for style compliance to verify adherence to established standards. This process helps identify potential areas for improvement in formatting, organization, and naming conventions.

Does this style guide cover dynamic resource creation and security in Terraform?

Yes, the style guide covers dynamic resource creation and security. It offers best practice recommendations for these areas, alongside guidelines for version pinning and standard formatting for optimal infrastructure code maintenance.

When should I use a Terraform style checker for infrastructure as code?

You should use a Terraform style checker when writing new modules or reviewing existing configurations. It verifies adherence to established standards, ensuring your infrastructure as code maintains optimal readability and consistency.