tg-migrate-help

Explains Terraform-to-Terragrunt migration phases, commands, and MCP server configuration.

Updated Jul 22, 2026
One-click install
npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill tg-migrate-help-trigent-software-pvt-ltd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tg-migrate-help
Source: https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc/tree/main/plugins/terragrunt-migrate/skills/tg-migrate-help
Command: npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill tg-migrate-help-trigent-software-pvt-ltd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Migrating a legacy Terraform repository to Terragrunt involves many phases, commands, and environment-specific steps that are hard to remember. This Skill provides an on-demand reference for the full migration workflow so you always know which command to run next and what each phase produces. ## Core Features & Use Cases - Phase Overview: Describes all 6 migration phases (analyse, scaffold, populate, import, validate, pipeline) with their purposes, MCP tools, outputs, and human checkpoints. - Command Reference: Documents utility commands like /tg-migrate-fix for bulk changes across environments and /tg-migrate-status for progress tracking. - Environment Matrix: Lists the 13 target environments across US and UK Azure regions with dev, staging, and prod tiers, including DR secondary designations. - Use Case: You are mid-migration and unsure whether to run import or validate next for uk-uksouth-staging. Invoke this Skill to review the phase order, the zero-destruction validation gate, and the exact command syntax. ## Quick Start Ask the assistant to show the Terragrunt migration workflow and explain which command to run for your current phase.

Frequently Asked Questions about tg-migrate-help

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

FAQPage Schema
How do I migrate Terraform to Terragrunt?

Follow six phases with dedicated slash commands: analyse the legacy repo, scaffold the Terragrunt structure, populate each environment, generate import scripts, validate with terragrunt plan, and finalize the pipeline. Each phase has a human checkpoint before proceeding.

What is the order of Terraform to Terragrunt migration phases?

The order is analyse, scaffold, populate, import, validate, then pipeline. Populate, import, and validate repeat per environment, starting with dev tiers, then staging, then prod across all regions.

How does the zero-destruction validation gate work in Terragrunt migration?

The validate phase runs terragrunt plan and checks that zero resources would be destroyed. Any destroy in the plan means FAIL, and you must fix the import configuration before retrying validation.

How do I apply bulk changes across all Terragrunt environments?

Use the /tg-migrate-fix command with a target path and description. It dry-runs the bulk replace or input update first, then applies changes across all populated environments only after your approval.

What MCP server is required for Terragrunt migration tools?

The tools are served by terragrunt-migration-server, a FastMCP server registered in the opencode configuration file. It exposes tools like migration_analyse_repo, migration_scaffold, and migration_run_plan.