stark-terragrunt-review

Reviews Terragrunt orchestration HCL across multiple LLM agents for dependency, state, and include issues.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/21StarkCom/stark-skills --skill stark-terragrunt-review-21starkcom
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: stark-terragrunt-review
Source: https://github.com/21StarkCom/stark-skills/tree/main/runtime-overrides/codex/skill/stark-terragrunt-review
Command: npx skills add https://github.com/21StarkCom/stark-skills --skill stark-terragrunt-review-21starkcom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Terragrunt live repos and catalogs hide orchestration-layer bugs — dependency cycles, unsafe mock outputs, broken state isolation, and tangled include hierarchies — that plain Terraform linters never see. This skill audits that orchestration layer with multiple independent LLM reviewers and merges their findings into one cross-validated report. ## Core Features & Use Cases - Multi-agent review: Dispatches one or more configured LLMs (claude, codex, gemini) as independent subagents, then merges and cross-validates their findings with severity filtering. - Orchestration-focused rubric: Checks dependency/DAG correctness, mock-output schemas, remote_state and generate blocks, state key isolation, include hierarchy, git source refspecs, and the DRY values pattern. - Consent-gated safety: Dry-run preview, explicit consent before sending HCL to provider CLIs, and fail-closed flags for scanner execution and PR posting. - Use Case: Point it at a live/prod Terragrunt tree before a rollout to catch a dependency cycle and a mock-output mismatch across environments, with findings confirmed by two independent models. ## Quick Start Ask the assistant to review the Terragrunt live directory for dependency and state issues, starting with a dry-run preview before approving the multi-agent dispatch.

Frequently Asked Questions about stark-terragrunt-review

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

FAQPage Schema
How do I review a Terragrunt repository for dependency and state issues?▼

Run the skill against the catalog or live directory path; it first performs a dry-run preview listing the exact HCL files and resolved providers. After you explicitly consent, it dispatches the configured LLM agents and returns a merged, severity-filtered report.

What is the difference between Terragrunt review and Terraform review?▼

This skill covers only the orchestration layer: dependency graphs, mock outputs, remote_state, generate blocks, and include hierarchies. Resource and module HCL is explicitly deferred to the stark-terraform-review skill.

Can I run a Terragrunt review with multiple LLMs like Gemini and Codex?▼

Yes, pass --agents gemini,codex or set iac_review.agents in config. Each agent reviews independently as its own subagent, and findings agreed upon by multiple agents are marked as cross-validated.

Does Terragrunt review work in a directory without git?▼

Yes, pass the explicit path, omit --changed, and skip git preflight. The dispatcher scans the full matching HCL tree, and PR posting flags should be left off unless separately requested.

Why does the Terragrunt review require consent flags before running?▼

The dispatcher embeds selected HCL contents in prompts sent to external provider CLIs, and Terragrunt trees can contain secrets and executable run_cmd expressions. Consent gates prevent unapproved data dispatch and execution of repository-controlled configuration.