agentleFS
Sign inStart free
alexderzalexderz/agentic-toolbox/skills/lang-terraform/SKILL.md

lang-terraform

Skill5 starsChanged 47 days agoMITView on GitHub

use this when writing or reviewing Terraform / HCL — *.tf, *.hcl. do not use for general YAML or for Docker.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Read the plan. Do not apply in this skill.

    line 23
  2. Very specific:

    No secrets in .tf / committed .tfvars.

    line 50
  3. Distinctive:

    No access keys in the tree.

    line 56

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Terraform

No scripts/. Process skills that may load with this one: load-with list.

Iron law

State is sensitive. Plans are read. Secrets stay out of VCS.

Tooling / verify

terraform fmt -check
terraform validate
terraform plan

Read the plan. Do not apply in this skill.

Idioms a linter misses

  • Remote state with locking when the project already has it.
  • Pin required_providers and Terraform version as the root module already does.
  • for_each over count for sets.
  • Variables for anything that changes by env. No copied prod IDs in a public file.
  • Expand-contract for destructive destroys.
  • ignore_changes only with a named reason.

Errors

  • Failed plan is a stop. Do not -auto-approve to hide it.

Testing

  • terraform plan against the real backend is the default test. terraform plan -lock=false is not a substitute.
  • terraform test / terratest only if the repo already has it.

PR review

  • Plan attached or reproducible from the module.
  • IAM not widened (* actions).
  • No secrets in .tf / committed .tfvars.
  • State backend unchanged unless the ticket says so.

Security

  • Least-privilege IAM. Do not widen *.
  • No access keys in the tree.
  • State contains secrets — treat backends as sensitive.

Always

  • fmt + validate + a plan you read.

Ask first

  • State migration.
  • New cloud account or region.
  • Destroy of existing resources.

Never

  • Secrets in VCS.
  • apply without a plan you read.
  • Force-unlock as a habit.
  • -auto-approve as the default path.

Red flags

  • "I'll apply -auto-approve"
  • "The secret is just a variable"
  • "force-unlock, it's stuck"

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free