check-moduleCheck a Terraform module directory with fmt, validate and tflint and report what passed, what failed and what was skipped. Use whenever the user asks whether a module is clean, valid or lint-free, asks to verify Terraform changes you just made, or wants a check run before a commit: "does this valida
explain-planExplain a Terraform plan in plain language that cuts straight to what matters - verdict first, then what changes, then what could hurt. Use this whenever the user pastes or points at plan output (`terraform show -json plan.out`, a plan JSON export, or a plan file that can be rendered that way) and w
fix-review-findingsWork through a review-module report (APPLY-CALYPSE-REPORT.md) one finding at a time: the user picks the findings and whether to commit, then terraform-author fixes each finding in report order, the module is checked after every fix, and a hand-off table closes the run. Slash command only; invoke it
look-up-schemaLook up the exact schema of a Terraform provider, resource or data source: which attributes exist, which are required, optional, computed, sensitive or deprecated, and which nested blocks exist. Use before writing or editing a resource block, and whenever you are unsure of an argument name, type or
onboard-toolchainBootstrap or improve the tooling around any Terraform repository through a short interview: version pinning, fmt/validate, tflint, trivy or checkov, OPA/conftest policy, terraform-docs, pre-commit, a local task runner, CI integration, dependency automation, and repo hygiene, with tool versions taken
review-moduleReview and grade Terraform (HCL) code, a whole repository or a feature branch, as the engineer who has to run the apply: what would terraform plan print, and can the code predict it. Reads the code against an eight-category rubric, and writes APPLY-CALYPSE-REPORT.md with a letter grade, a BLOCK / AP
trace-change-impactTrace what a Terraform change touches: which blocks changed, how module variables and outputs changed, and which root modules reach a changed module. Use before editing or merging a module that other roots call, when the user asks "what does this change affect", "who uses this module", or "is this c
writing-terraformWrite or change Terraform so the plan does exactly what was asked and nothing else: every argument checked against the locked provider schema, every value traced to a reference, a variable or the user, data stores hardened and protected by default, a moved block for every address change, replace-for