Skills

modulestf: agent skills to review and modify Terraform modules according to terraform-aws-modules rules

Engineers who want to review and modify reusable Terraform modules according to terraform-aws-modules rules in a coding agent are best served by first running one of these skills on a PR review with a confirmation point; before use, you must configure a HashiCorp Terraform MCP server named terraform for the agent, otherwise rules that depend on provider facts will not run and review conclusions are at best uncertain.

Official source · modulestf

Install

git clone https://github.com/modulestf/modulestf.git && ln -sfn "$PWD"/modulestf/.agents/skills/* ~/.claude/skills/

Who it's for

  • These agent skills are for engineers who write and maintain Terraform modules in Claude Code or Codex and want to review or modify modules according to the written rules of the terraform-aws-modules family. It runs on your own machine, using your own GitHub login.
  • Currently only one rule profile ships with it: terraform-aws-modules. If your project needs rules for other families, the official evidence does not state their applicability.
  • Before first use, you must configure a Terraform MCP server named terraform for the agent. The official documentation is explicit: without it, rules that require provider facts will be reported as not run, and a PR review can at best reach an "uncertain" conclusion.
  • If you're unsure whether your module belongs to this family, start with the low-risk review below.

First attempt in 3 minutes

Prerequisites: Claude Code is installed, and you have connected the HashiCorp Terraform MCP server to the agent under the name terraform following the official instructions. Side effects to declare: the review workflow clones the PR into a temporary directory and runs terraform init -backend=false and terraform validate in each example — the official documentation states this writes no state and uses no real backend, but it does execute Terraform commands in the temporary directory.

  1. Clone the repository and put all four skill directories into Claude Code's skills directory:
git clone https://github.com/modulestf/modulestf.git
ln -sfn "$PWD"/modulestf/.agents/skills/* ~/.claude/skills/
  1. Start a low-risk task in Claude Code: run a review on a PR for an existing reusable Terraform module (a diagnostic operation). Success signal: the agent produces a verdict, findings, and a suggested PR comment draft.
  2. Key confirmation point: nothing is published until you confirm; when confirming, you also choose the review event — publish the comment, approve, or request changes, limited to these three as officially listed. Whether the review process reads or writes other files or accesses the network beyond the commands above, the official documentation does not itemize; treat it as unknown.
  3. If some rules report not run, first check whether the terraform MCP server is properly connected.

Use cases

  1. PR review: in Claude Code, have the agent review an open PR according to the terraform-aws-modules rules. The workflow clones the PR into a temporary directory, runs terraform init -backend=false and terraform validate in each example, then produces a verdict, findings, and a proposed comment; nothing is published until you confirm the comment and choose the review event.
  2. Post-review changes: after the review produces a verdict, have the agent modify the module as the review requires. The official documentation states that these skills "review, change and create reusable Terraform modules" and help complete the changes the review calls for; the changes modify module files, so confirm which files are involved before starting. The official evidence does not list step-by-step details of this change workflow; what can be confirmed is that it performs changes according to the profile's rules, provided the review's findings exist first.

Boundaries of use

  • Explicit side-effect limits (official wording): no skill runs terraform apply, writes state, or uses a real backend; no skill merges, pushes to a pull request, or resolves threads. The review process publishes no comments or review events before confirmation. Note: the official documentation only lists the limits above and does not state that the change workflow is read-only — these skills are positioned to change and create modules as the review requires, and that workflow modifies module files, so verify the scope yourself before making changes.
  • Runtime prerequisites: runs locally in Claude Code or Codex, using your own GitHub login; installation is done by copying or symlinking the four directories, with the skills directories being ~/.claude/skills/ and ~/.agents/skills/ for the two platforms respectively. Evidence for other installation methods or platforms is not stated.
  • Reviewing requires first cloning the PR and running terraform init/validate in a temporary directory, so a Terraform environment is needed locally.
  • Key unconfirmed information: the official evidence does not state supported Terraform versions, provider coverage, compatibility with other agents, or the specific operation lists of each workflow beyond "review, change and create"; the full scope of file and network access for the review and change processes is also not itemized. It is recommended to verify in your own environment before use.