tf-versions

Generate Terraform required_providers blocks from usage analysis.

1|Updated Apr 30, 2026

Search Tags:#automation #devops #infrastructure as code #terraform #module #required_providers

Ready to run

npx skills add https://github.com/subhamay-bhattacharyya/aws-csv-data-pipeline --skill tf-versions

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tf-versions
Source: https://github.com/subhamay-bhattacharyya/aws-csv-data-pipeline/tree/main/.claude/skills/tf-versions
Command: npx skills add https://github.com/subhamay-bhattacharyya/aws-csv-data-pipeline --skill tf-versions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the creation of versions.tf files by generating precise required_providers blocks, reducing configuration errors and maintenance overhead.

Core Features & Use Cases

Generate provider declarations for Terraform modules based on actual usage.
Maintain clean separation between provider versions and backend version constraints.
Use Case: When scaffolding a new infrastructure module, quickly produce the versions.tf with correct provider sources and version constraints, ensuring consistency and compatibility.

Quick Start

Use the tf-versions skill to generate a versions.tf file that declares the required providers for your Terraform module.

Frequently Asked Questions about tf-versions

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

FAQPage Schema

How do I generate a required_providers block for a Terraform module?▼

Generate a required_providers block for a Terraform module by analyzing provider usage within the module code and outputting a versions.tf file containing only the necessary provider sources and version constraints.

What is the best way to manage Terraform module provider declarations?▼

Managing Terraform module provider declarations involves automating the creation of versions.tf files to ensure modules specify only necessary providers with correct source identifiers, reducing configuration errors and maintenance overhead.

Why does my Terraform module include unused providers in the required_providers block?▼

Unused providers appear in required_providers blocks when declarations are managed manually. Automating versions.tf generation based on actual usage analysis ensures modules specify only the necessary providers.

How do I separate provider versions from backend version constraints in infrastructure as code?▼

Separate provider versions from backend version constraints in infrastructure as code by generating a dedicated versions.tf file that maintains clean separation and ensures correct provider source identifiers and version constraints.

Can I automate versions.tf creation when scaffolding new infrastructure modules?▼

You can automate versions.tf creation when scaffolding new infrastructure modules by analyzing provider usage to quickly produce accurate required_providers blocks, ensuring consistency and compatibility across the module.