modulestf skill
With modulestf, the agent reviews and maintains Terraform modules, seeking separate approval before posting findings to GitHub.
- 366 ★ on the repository
- Last commit
- Apache-2.0
Extended access
Why this level
- The agent can edit a local module and run bounded checks; Terraform executes provider plugins from that project.
Install
- Works in
Manual install
git clone https://github.com/modulestf/modulestf.git
mkdir -p ~/.claude/skills
ln -sfn "$PWD"/modulestf/.agents/skills/* ~/.claude/skills/ # Claude CodeFirst Quick start path for Claude Code. Check for existing skills with the same names; the README next shows Codex setup.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The agent can edit a local module and run bounded checks; Terraform executes provider plugins from that project.
This is third-party code. Review the repository files before installing.
What it does
modulestf provides separate instructions for Terraform review, maintenance and scope decisions. The agent checks a change against its module-family profile, reads provider schemas and reports file-specific findings. A separate workflow handles local corrections. Pull-request review prepares a verdict and comment for user confirmation before posting. Maintenance does not push changes or resolve discussions. A terraform-aws-modules profile is included.
Who it is for. Terraform module maintainers reviewing external pull requests and keeping provider-resource changes consistent.
Good fit when
- Before accepting an external pull request, you check it against module-family rules.
- After review, you want to correct a specific finding in your checkout.
- When a provider upgrade changes schemas, you prepare migration notes.
- For a proposed feature, you need to decide whether it belongs in this module.
Not a fit when
- You want automatic infrastructure application through terraform apply.
- Terraform MCP and mtf-facts cannot be prepared for a conclusive review.
- Every module family needs a ready profile without adaptation.
Example request
Review this Terraform pull request and show findings and the draft review without posting.Limitations
The three Terraform skills share guidance with `change-scope`; install all four directories side by side. Provider facts require Terraform MCP; related checks remain unperformed without it. A conclusive pull-request review needs local tools including mtf-facts and isolation support, so check task-specific dependencies. Even init and validate execute provider plugins from the proposed change; do not authorize extra hooks or broader access for unreviewed code.
How to disable. Remove installed skill links or copies and disable unused Terraform MCP access. Saved reports and local edits remain.
FAQ
Do the skills apply infrastructure?
No. Under these instructions, the agent does not run `terraform apply` or change real infrastructure state.
How does triage differ from review?
It checks scope and provider-independent rules without validation or approval.
How do I show uncommitted work?
Provide `git diff`; ordinary local review reads committed changes.
Who authorizes posting?
The user confirms the comment text and review event: comment, approval or change request.
Does pre-commit run automatically?
No. Repository hooks require the user to explicitly mark that run as trusted.
Discussion
No questions or reviews yet.
Related
SkillsTerraform Skill
Terraform & OpenTofu Skill for AI Agents
A Terraform and OpenTofu best-practices skill: tests, modules, state, CI/CD and security scanning for AWS, Azure and GCP
A Terraform skill for Claude Code, Codex, Antigravity and Gemini CLI: cuts hallucinations and keeps code on HashiCorp's official practices
Official HashiCorp skills for Terraform and Packer: HCL style, modules, tests, imports, Stacks, provider development and image builds
31 DevOps skills for Claude Code and Codex: config generators, validators and a Kubernetes debugger for Terraform, Helm, CI and Docker
A Rust MCP server for Terraform: the agent inspects a project, builds a saved plan, reviews its risks and applies that same plan
KubeShark skill: the agent finds the failure mode first, then writes manifests, Helm and Kustomize to official practice with a rollback plan
README in short
The optional plan pass uses a separately selected read-only role. New module creation and external-change review have different permission requirements.
README badge
Original SKILL.md
--- name: terraform-module-maintainer description: Create, restructure, change, fix, and upgrade reusable Terraform modules for any provider, following a module profile (default terraform-aws-modules). Use for new modules, feature changes, fixing review findings, resolving review feedback with draft replies, and provider major upgrades. Not for general Terraform questions (use terraform-skill). --- # Terraform Module Maintainer Create and maintain production-ready Terraform modules for any provider with complete feature coverage. Project-specific conventions come from a profile; the default profile is `terraform-aws-modules`. ## When to Use This Skill **Activate when:** - Creating a new Terraform module from scratch (any provider: AWS, GCP, Azure, etc.) - Restructuring an existing module to meet profile standards - Adding comprehensive feature coverage to a partial module - Changing or fixing an existing module (feature request, review finding, bug) - Working through review feedback on a change - findings, review comments, bot comments - and drafting the replies - Upgrading a module to a new provider major version **Don't activate for:** - General Terraform questions (use `antonbabenko/terraform-skill` plugin) - Reviewing a change without editing it (use `terraform-module-reviewer`) ## Modes > Three modes are written out below; Resolve feedback lives in its reference. | Mode | When | Workflow | |------|------|----------| | Full create | New module, restructure, full coverage pass | Module Creation Workflow below | | Targeted change | Feature, fix, review finding on an existing module | Targeted Change Workflow below | | Resolve feedback | A set of review feedback items on a change: decide each, fix, draft replies | [resolve-feedback.md](references/resolve-feedback.md) | | Provider upgrade | Provider major version bump | Provider Upgrade Workflow below | Before editing in Full create, Targeted change or Resolve feedback mode, apply [change-scope](../change-scope/SKILL.md) through [module-scope.md](references/module-scope.md) and the profile's [scope file](profiles/terraform-aws-modules/scope.md): refuse or redirect a misfit to one destination from [Where a misfit goes](../change-scope/references/principles.md#where-a-misfit-goes), and keep a fix inside its finding. ## Profiles A profile holds the conventions of one module family: templates, CI workflows, release config, README layout, and quality gate details. The generic workflow and `references/` stay provider-neutral.