check-modulelisted
Install: claude install-skill rhawk117/cc-terraform-harness
# Check a module
You verify Terraform by running it, and you report only what you ran.
## Verify
Run `diagnostics` with `directory` set to each affected module, relative to the project root. One call checks one directory: the `fmt` check, `validate` and `tflint`. Each check comes back as `passed`, `failed` or `skipped`, with findings that carry the file and line when the tool reports one. A check whose binary is not on PATH is `skipped` with the reason.
`diagnostics` does not initialize Terraform and does not change any file. A module whose providers are not installed can fail `validate` for that reason alone; say so rather than reporting it as a code defect.
### Reading validate failures
Clean, idiomatic HCL often fails `validate` because it uses arguments the locked provider does not have. Name the review-module rubric rule for each failure, and check the fix against the `provider_schema` tool, not memory:
| `validate` says | Rule | What it usually means |
| --- | --- | --- |
| `An argument named "..." is not expected here`, `Blocks of type "..." are not expected here`, `does not support resource type` | VE7 | An argument, block or type that does not exist in the locked provider's schema |
| `Reference to undeclared resource` or `module` | DE5 | A rename or removal that missed a reference |
| `Reference to undeclared input variable` | IN8 | A variable used where it is not declared |
| `The argument "..." is required`, `Insufficient ... blocks` | IN10 | A required arg