terraform-module-ops

Locates Terraform resources, verifies state backends, validates locally, and flags drift before edits.

1|Updated Jun 11, 2026
One-click install
npx skills add https://github.com/sergeyitaly/claude-skill-deployer --skill terraform-module-ops
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: terraform-module-ops
Source: https://github.com/sergeyitaly/claude-skill-deployer/tree/main/skills_library/terraform-module-ops
Command: npx skills add https://github.com/sergeyitaly/claude-skill-deployer --skill terraform-module-ops

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Editing Terraform code without first understanding the codebase structure, state backend, or existing drift can lead to failed deployments, unintended infrastructure destruction, or costly outages. This Skill eliminates that risk by providing a structured pre-change navigation and safety workflow for Terraform projects.

Core Features & Use Cases

  • Module-to-Resource Mapping: Quickly locate which files or modules own specific Terraform resources, eliminating hours of manual grepping.
  • State Backend & Version Verification: Identify the configured state backend, provider versions, and required Terraform version to avoid misconfiguration errors.
  • Safe Local Validation: Run Terraform fmt and validate workflows locally without cloud credentials, with a built-in fallback for backend initialization failures.
  • Drift & Risk Flagging: Detect documented known drift and flag high-risk operations like full apply or destroy that require explicit user approval.
  • Use Case: If you need to update an Azure Virtual Network resource in a large Terraform codebase, use this Skill first to confirm the resource's location, check for drift, and validate your changes locally before running a plan.

Quick Start

Use the terraform-module-ops skill to map all resources in your Terraform root directory and identify any known drift before you make changes to .tf files.

Frequently Asked Questions about terraform-module-ops

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

FAQPage Schema
How do I check Terraform code for drift before modifying infrastructure?

To check Terraform code for drift before modifying infrastructure, you can map resources in your root directory and identify known drift. This prevents unsafe, uninformed changes that risk production outages or unintended resource destruction.

Can I run Terraform fmt and validate locally without cloud credentials?

Yes, you can run Terraform fmt and validate workflows locally without cloud credentials. This safe local validation includes a built-in fallback mechanism to handle potential backend initialization failures.

How do I locate which Terraform module owns a specific cloud resource?

To locate which Terraform module owns a specific cloud resource, you can perform a module-to-resource mapping. This quickly identifies the files or modules managing the resource, eliminating hours of manual grepping.

What is the safest way to navigate a large Terraform codebase before an apply?

The safest way to navigate a Terraform codebase before an apply is to use a structured pre-change workflow. This verifies the state backend, provider versions, and flags high-risk operations requiring explicit user approval.

Does Terraform drift detection require cloud provider authentication?

No, Terraform drift detection and local validation do not require cloud provider authentication. You can execute fmt and validate workflows locally without cloud credentials while still identifying documented known drift.

Why does modifying Terraform infrastructure-as-code without checking state backend cause outages?

Modifying Terraform infrastructure-as-code without checking the state backend causes outages because it risks misconfiguration errors and unintended resource changes. Verifying the state backend, provider, and Terraform versions prevents these failed deployments.