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.
In this repository29 other files it gives its agents.
- AGENTS.mdAGENTS.md
- address-pr-commentsSkill
- build-and-scan-container-imageSkill
- execute-database-migrationSkill
- generate-adrSkill
- generate-service-documentationSkill
- get-pr-commentsSkill
- incident-triageSkill
- install-dev-toolsSkill
- prepare-releaseSkill
- remediate-dependency-vulnerabilitiesSkill
- review-configurationSkill
- twg-agentic-searchSkill
- twg-artifactsSkill
- twg-code-reviewSkill
- twg-confluenceSkill
- twg-context-discoverySkill
- twg-engineering-workSkill
- twg-jira-resolve-merged-workSkill
- twg-jiraSkill
- twg-operational-healthSkill
- twg-responsibility-routingSkill
- twgSkill
- twg-space-creationSkill
- twg-status-rollupsSkill
- validate-and-deploy-kubernetesSkill
- validate-documentationSkill
- validate-github-actionsSkill
- verify-service-healthSkill
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
- Distinctive: line 25
Run formatting, syntax, schema, lint, and policy validation.
- Distinctive: line 32
Verify post-apply state, outputs, health, and drift.
- Distinctive: line 36
Default to read-only validation or plan mode.
- Distinctive: line 40
Do not bypass policy violations or state locking.
≈ “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.
Files
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; defaultstaging.mode:validate,plan,detect-drift,apply,destroy, orcost; defaultvalidate.targetResources: optional resource scope.reviewedPlanArtifact: required forapply; identifies the reviewed plan by path, ID, or checksum.format:summary,json, or native plan artifact; defaultsummary.
Workflow
- Detect the framework, backend, variables, provider versions, and environment.
- Run formatting, syntax, schema, lint, and policy validation.
- For
plan,cost, ordetect-drift, produce a reviewable artifact. - Classify creates, updates, replacements, and destroys; identify sensitive values.
- Require explicit approval for apply, destroy, production, or destructive plans.
- For
apply, require and verifyreviewedPlanArtifactbefore mutation; reject a regenerated or mismatched plan. - Apply the exact verified plan, never a newly generated unreviewed plan.
- 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.
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
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.

