terraform-state-manager

Refactor, import, or remove Terraform state with incremental safety checks.

218|33|Updated Jan 7, 2026

Search Tags:#terraform #state-management #infrastructure-as-code #resource-import #backend-migration #state-rm #state-mv

Ready to run

npx skills add https://github.com/first-fluke/fullstack-starter --skill terraform-state-manager

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: terraform-state-manager
Source: https://github.com/first-fluke/fullstack-starter/tree/main/.agents/skills/terraform-state-manager
Command: npx skills add https://github.com/first-fluke/fullstack-starter --skill terraform-state-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams safely refactor Terraform state, import existing resources into Terraform management, rename or move resources between modules, and migrate backends without destroying resources.

Core Features & Use Cases

Import Resources: Bring existing cloud resources under Terraform control with accurate state.
State Refactoring: Move or rename resources across modules or resources without data loss.
Backend Migration: Switch state backends (local, GCS, S3) with minimal downtime and risk.
State Cleanup: Remove resources from state control while keeping them running in the cloud.

Quick Start

Start with backing up your current state, then perform incremental operations like import, state mv, or state rm, and always verify with terraform plan before applying.

Frequently Asked Questions about terraform-state-manager

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

FAQPage Schema

How do I import existing cloud resources into Terraform state without destroying them?▼

To import existing resources into Terraform state safely, you back up your current state, perform the import incrementally, and verify the outcome with terraform plan before applying any changes.

What's the best way to move or rename resources between Terraform modules?▼

The best way to move or rename resources between Terraform modules is using state mv operations incrementally, backing up state beforehand, and verifying changes with terraform plan to prevent data loss.

How do I migrate Terraform state backends between local, S3, and GCS?▼

Migrating Terraform state backends between local, S3, and GCS requires backing up your current state, switching the backend configuration, and verifying with terraform plan to minimize downtime and risk.

Can I remove resources from Terraform state while keeping them running in the cloud?▼

Yes, you can remove resources from Terraform state while keeping them running in the cloud by using state rm, backing up state first, and verifying the removal with terraform plan to ensure safety.

Why should I back up Terraform state before refactoring or importing resources?▼

You should back up Terraform state before refactoring or importing resources to enforce safety, prevent data loss during state mv or state rm operations, and ensure you can verify changes with terraform plan.

When do I need to remove resources from Terraform state management?▼

You need to remove resources from Terraform state management when refactoring modules or cleaning up state control, using state rm incrementally and verifying with terraform plan to keep resources running safely in the cloud.