Reviewing pull requests for terraform-aws-modules has always taken a lot of my time. It was a problem for a very long time, and I recorded livestreams of myself doing it. I cannot skip it: merging something that is not great is a way to disaster and lost trust.
AI lets everyone write code now, and coding agents open pull requests for Terraform modules. A person still reads each one.
A model already knows how to write good Terraform. For that part I maintain terraform-skill , a skill for Terraform and OpenTofu with testing, module, CI/CD and production patterns. What a model does not know is what we allow and expect in the modules. Can a module create a KMS key? Which regions may examples use? Does this addition belong in the module at all? terraform-aws-modules has no written scope policy, so the model guesses and I read the guess.
I released the pieces that write it down and apply it. modulestf is four agent skills for Claude Code and Codex, with a profile of the rules.…