agentleFS
ByronScottJonesByronScottJones/Agents/skills/validate-and-deploy-iac/SKILL.md

validate-and-deploy-iac

Skill7 starsChanged 2 months agoMITView on GitHub

Use when validating, planning, detecting drift in, or applying infrastructure as code. Supports Terraform and extensible IaC workflows with plan-first safety gates, destructive-change review, and explicit approval before mutation.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run formatting, syntax, schema, lint, and policy validation.

    line 25
  2. Distinctive:

    Verify post-apply state, outputs, health, and drift.

    line 32
  3. Distinctive:

    Default to read-only validation or plan mode.

    line 36
  4. Distinctive:

    Do not bypass policy violations or state locking.

    line 40

≈ “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

Validate and Deploy Infrastructure as Code

Validate infrastructure changes and, when explicitly authorized, promote them through a plan-first workflow.

Parameters

  • projectPath: IaC root; default workspace root.
  • framework: terraform, bicep, pulumi, cloudformation, or auto-detect.
  • environment: target environment; default staging.
  • mode: validate, plan, detect-drift, apply, destroy, or cost; default validate.
  • targetResources: optional resource scope.
  • reviewedPlanArtifact: required for apply; identifies the reviewed plan by path, ID, or checksum.
  • format: summary, json, or native plan artifact; default summary.

Workflow

  1. Detect the framework, backend, variables, provider versions, and environment.
  2. Run formatting, syntax, schema, lint, and policy validation.
  3. For plan, cost, or detect-drift, produce a reviewable artifact.
  4. Classify creates, updates, replacements, and destroys; identify sensitive values.
  5. Require explicit approval for apply, destroy, production, or destructive plans.
  6. For apply, require and verify reviewedPlanArtifact before mutation; reject a regenerated or mismatched plan.
  7. Apply the exact verified plan, never a newly generated unreviewed plan.
  8. Verify post-apply state, outputs, health, and drift.

Safety

  • Default to read-only validation or plan mode.
  • Approval is mandatory for every apply or destroy operation and cannot be disabled by a parameter.
  • Redact secrets from plans, logs, and artifacts; redaction cannot be disabled.
  • Reject apply when the reviewed plan artifact is missing or does not match.
  • Do not bypass policy violations or state locking.

Output

Return framework, environment, validation results, plan summary, drift status, destructive changes, approvals, applied resources, and next steps.

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.