Manage Terragrunt infrastructure-as-code configurations: define stacks and units, orchestrate remote state in S3/DynamoDB, deploy across multiple AWS accounts, and maintain classic or stack-based live repository structures.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A Claude Code skill providing best practices guidance for Terragrunt infrastructure-as-code with OpenTofu/Terraform.
Important: Catalog and Live repositories should be separate Git repositories. The live repo consumes units and stacks from the catalog via Git URLs.
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
┌─────────────────────────────────────────────────────────────────────┐
│ SEPARATE REPOSITORIES │
├─────────────────────────┬─────────────────────────┬─────────────────┤
│ Module Repos │ Catalog Repo │ Live Repo │
│ (terraform-aws-*) │ (infrastructure- │ (infrastructure-
│ │ <org>-catalog) │ <org>-live) │
├─────────────────────────┼─────────────────────────┼─────────────────┤
│ • OpenTofu modules │ • units/ (wrappers) │ • root.hcl │
│ • Semantic versioning │ • stacks/ (templates) │ • account.hcl │
│ • Terratest │ • References modules │ • Deployments │
│ • Pre-commit hooks │ via Git URLs │ • Consumes │
│ │ │ catalog │
└─────────────────────────┴─────────────────────────┴─────────────────┘
▲ ▲ │
│ │ │
└─────────────────────────┴────────────────────────┘
Live repo references both via Git URLs
┌───────────────────────────────────────────────────────────────┐
│ SEPARATE REPOSITORIES │
├─────────────────────────────────┬─────────────────────────────┤
│ Catalog Repo │ Live Repo │
│ (infrastructure-<org>-catalog)│ (infrastructure-<org>-live)
├─────────────────────────────────┼─────────────────────────────┤
│ • modules/ (OpenTofu modules) │ • root.hcl │
│ • units/ (module wrappers) │ • account.hcl │
│ • stacks/ (unit compositions) │ • Deployments │
│ • Discovered via `tg catalog` │ • Consumes catalog via Git │
│ • Single versioning strategy │ • `tg scaffold` for new │
└─────────────────────────────────┴─────────────────────────────┘
▲ │
└──────────────────────────────┘
Live repo references catalog
Trade-offs:
| Aspect | Option A (Separate Module Repos) | Option B (Modules in Catalog) |
|---|---|---|
| Versioning | Independent per module | Single catalog version |
| CI/CD | Dedicated pipeline per module | One pipeline for all |
| Complexity | More repos to manage | Simpler structure |
| Team ownership | Clear boundaries | Shared ownership |
terragrunt catalog | Discovers units/stacks | Discovers modules too |
"../unit" → dependency outputs)enabled and skip_outputsassume-role-with-web-identity)--provider-cache)This skill is distributed via Claude Code marketplace using .claude-plugin/marketplace.json.
/plugin marketplace add jfr992/terragrunt-skill
/plugin install terragrunt-skill@jfr992
# Clone to Claude skills directory
git clone https://github.com/jfr992/terragrunt-skill.git ~/.claude/skills/terragrunt-skill
After installation, try:
"Create a Terragrunt stack for a serverless API with Lambda, DynamoDB, and S3"
Claude will automatically use the skill when working with Terragrunt code.
# Ask Claude to scaffold a new catalog
"Create a new infrastructure catalog with units for S3, DynamoDB, and Lambda"
npx claudepluginhub jfr992/terragrunt-skill --plugin terragrunt-skillTerraform and Terraform Cloud - infrastructure as code
laurigatesTerraform module creation and infrastructure planning
rohitg00DevOps skills for Claude Code: Terraform/OpenTofu workflows, AWS infrastructure management, safety-first IaC practices, and parallel agent orchestration
lgbarnBuild reusable Terraform modules
jeremylongshoreTerraform Cloud workspace management, run monitoring, and registry lookups
bendruckerComplete Terraform and OpenTofu expertise system for all cloud providers with 2025 features. PROACTIVELY activate for: (1) ANY Terraform/OpenTofu task, (2) Terraform 1.10 ephemeral values and 1.11 write-only arguments, (3) AzureRM Provider 4.x (provider-defined functions, 1,101+ resources), (4) AWS Provider 6.0 GA breaking changes and migration, (5) OpenTofu 1.10/1.11 (OCI registry, state encryption, native S3 locking), (6) Ephemeral resources (azurerm_key_vault_secret, aws_secretsmanager_secret_version), (7) Policy-as-code with Sentinel/OPA/Checkov (NIST SP 800-53 Rev 5), (8) Terraform Stacks (GA) with Linked Stacks, (9) Testing with terraform test framework and Terratest, (10) Git Bash/MINGW path conversion issues on Windows, (11) Private module registry and no-code provisioning, (12) Cross-platform scripts with shell detection. Provides: Terraform 1.10/1.11 ephemeral and write-only patterns, AzureRM 4.x provider functions (normalize_resource_id, parse_resource_id), AWS 6.0 migration guidance, comprehensive ephemeral resource examples, Git Bash Windows compatibility, policy-as-code governance, OpenTofu state encryption, native S3 locking without DynamoDB, version-aware code generation, Trivy security scanning, cost estimation with Infracost, CLI mastery, and 2025 industry best practices across Windows (PowerShell/Git Bash), Linux, and macOS. Ensures enterprise-ready, compliant, scalable, governed infrastructure with policy enforcement and self-service capabilities.
JosiahSiegel