# Stack Terraform

> Reviews Terraform changes when plans, state, modules, providers, or drift need focused checks; discovers backend and version constraints without applying or changing shared infrastructure.

- Skill: `jovanipink/stack-terraform` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx get-skill add jovanipink/stack-terraform`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jovanipink/stack-terraform/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- License: MIT
- Author: JovaniPink (https://skillmd.com/u/jovanipink)
- Updated: 2026-11-15
- Page: https://skillmd.com/skills/jovanipink/stack-terraform

---


# Terraform Engineering Profile

Use this profile only after repository discovery identifies the stack. Read [focused checks](references/checks.md) when stack-specific gates or hazards determine the result.

## Workflow

1. Discover Terraform files, module structure, required providers, dependency lockfiles, backend declarations, workspaces, and repository scripts.
2. Follow repository-defined commands and pinned tool versions before suggesting defaults.
3. Review idiomatic design and material hazards, especially resource-address churn, unsafe `for_each` keys, sensitive state, provider defaults, lifecycle misuse, implicit dependencies, broad IAM, replacement, and drift.
4. Select proportionate gates from repository scripts, formatting, initialization with controlled backend behavior, validation, static analysis, policy checks, and reviewed plans without applying.
5. Review compatibility across Terraform and provider versions, module interfaces, state moves, import blocks, backend behavior, upgrade guides, and plan changes across environments.
6. Report every missing tool, skipped command, unsupported platform, or unavailable environment as incomplete rather than passing.

## Boundaries

- Do not invent one universal command or replace repository policy with generic preferences.
- Do not install, upgrade, publish, deploy, apply, or mutate shared state merely to run a gate.
- Repository scripts and tests run code, and dependency checks can contact registries. Run a gate only when the user asked for checks and trusts the repository. Otherwise, name it as the next safe gate.
- Treat `terraform init` and `terraform plan` against a real backend as provider access: they use credentials, can lock state, and call provider APIs. Prefer static checks and `terraform init -backend=false` with `terraform validate`. Run a real plan only with authorization.
- Separate static review, executed checks, build evidence, provider state, and live behavior.

## Output

Lead with the answer. Use the shortest format that retains the required evidence and limits; expand when requested or needed. The items below describe required content, not mandatory headings.

Return Discovery, Hazards, Commands selected, Results, Compatibility, Missing evidence, and Next safe gate.

## Example

Synthetic example; not an observed client result.

Input: A plan proposes replacing a database resource.

Output: Review the replacement cause, state address, provider version, and recovery evidence. A plan review does not authorize apply.

