tf-validations

Generate Terraform precondition assertions validating filenames, paths, and required keys.

1|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/subhamay-bhattacharyya/aws-csv-data-pipeline --skill tf-validations
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tf-validations
Source: https://github.com/subhamay-bhattacharyya/aws-csv-data-pipeline/tree/main/.claude/skills/tf-validations
Command: npx skills add https://github.com/subhamay-bhattacharyya/aws-csv-data-pipeline --skill tf-validations

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps prevent common Terraform configuration errors by validating important conventions early in the deployment process.

Core Features & Use Cases

  • Automatic Plan-time Checks: Generates precondition assertions that catch issues like invalid paths, missing keys, or improper naming before applying.
  • Enhanced Infrastructure Reliability: Enforces consistent standards across Terraform modules, reducing runtime errors and manual debugging.
  • Use Case: If you want to verify that all filenames in your configs are correctly formatted or that required keys are present in your JSON inputs, this Skill automates those checks with clear, actionable error messages.

Quick Start

Use the tf-validations skill to create a validation file that safeguards naming conventions and file paths in your Terraform modules.

Frequently Asked Questions about tf-validations

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

FAQPage Schema
How do I validate Terraform configurations for missing keys before deployment?

Validating Terraform configurations for missing keys involves generating precondition assertions that enforce required key presence and naming conventions during plan preparation, catching errors before deployment.

What is the best way to enforce naming conventions in Terraform modules?

Enforcing naming conventions in Terraform modules is best achieved by generating validation files with precondition guardrails that automatically check filename formats and path correctness, producing descriptive errors when standards are violated.

Can I check Terraform file paths and required JSON inputs during plan preparation?

Yes, you can check Terraform file paths and required JSON inputs during plan preparation by implementing automated precondition checks that verify path correctness and key presence, stopping invalid configurations before they are applied.

How do I prevent configuration errors in Terraform without manual post-deployment debugging?

Preventing configuration errors in Terraform requires implementing plan-time validations that generate descriptive errors for invalid paths or missing keys, eliminating the need for manual checks and post-deployment debugging.

Does this Terraform validation approach work without external dependencies?

Yes, this Terraform validation approach works without external dependencies by using built-in precondition scripts to generate assertion files that safeguard naming conventions and file paths directly within your modules.