modulestf/modulestf

Agent skills that review reusable Terraform modules against a written profile of the module family's rules, and help you make the change the review asks for. One profile ships today: terraform-aws-modules. They run in your coding agent (Claude Code or Codex) on your machine, with your own GitHub login.
The skills
Quick start
Everyday use
Reading a review
Limits
Advanced use
Requirements by task
Related repositories
## The skills
| Skill | You give it | You get back |
| terraform-module-pr-review | A pull request or commit URL, or owner/repo#123 | A verdict and a comment to post, after you confirm |
| terraform-module-reviewer | A module checkout and a diff, a base ref or a list of changed files | A list of findings. Read-only, no verdict |
| terraform-module-maintainer | A change to make, review feedback to work through, a module to create or a provider to upgrade | Edits in your checkout, a report of the checks it ran, and reply drafts |
| change-scope | A proposed addition, in any language or project | Whether it belongs in the thing being changed, and where it goes if not |
The pull request review calls the reviewer, and both call change-scope. The rules of the module family live in a profile: terraform-aws-modules.
## Quick start
1. Install the skills. Copy or symlink all four directories under .agents/skills/ side by side into your agent's skills directory: ~/.claude/skills/ for Claude Code, ~/.agents/skills/ for Codex. The three Terraform skills link into each other, so keep them together. change-scope also works alone.
bash
git clone https://github.com/modulestf/modulestf.git
mkdir -p ~/.claude/skills
ln -sfn "$PWD"/modulestf/.agents/skills/ ~/.claude/skills/ # Claude Code
mkdir -p ~/.agents/skills
ln -sfn "$PWD"/modulestf/.agents/skills/ ~/.agents/skills/ # Codex
2. Add HashiCorp's Terraform MCP server to your agent under the name terraform, so its tools appear as mcpterraformgetlatestproviderversion, mcpterraformsearchproviderdocs and mcpterraformgetproviderdetails. The skills read provider schemas from it, not from memory. Without it, every rule that needs a provider fact is reported as not run, so a pull request review is inconclusive at best.
3. Log in to GitHub with gh auth login as yourself, and install terraform, git and jq.
4. Ask your agent:
text
review terraform-aws-modules/terraform-aws-lambda#780
The skill clones the pull request into a temporary directory, runs terraform init -backend=false and terraform validate in each example the change touches, and shows you a verdict, the findings and the comment it would post. It posts nothing until you confirm the comment and its review event: comment, approve or request changes.
## Everyday use
Write requests in plain words. The examples show what each skill needs to hear.
### Review a pull request or a commit
text
review https://github.com/terraform-aws-modules/terraform-aws-lambda/pull/780
is terraform-aws-modules/terraform-aws-lambda#780 ready to merge?
what should I reply on terraform-aws-modules/terraform-aws-lambda#780?
review https://github.com/terraform-aws-modules/terraform-aws-lambda/commit/
You get a verdict, a comment with every finding and its suggested fix, the checks that could not run, and the state of the pull request's checks and threads. The skill proposes one review event (comment, approve or request changes) and asks once. Say "do not post" and it runs render-only: it shows the comment and posts nothing. A commit gets a plain commit comment with no approve or request changes.