القائمة
Designs and implements Terraform module tests for AWS-targeted modules. Covers terraform-native tests, validation gates, fixture composition, and risk-focused assertions for regressions, address migration, and unsafe changes.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Structures, writes, and reviews Terraform infrastructure code. Covers module layout, remote state, workspace strategy, variable and secrets handling, CI plan/apply pipeline, naming conventions, and multi-region deployment patterns (provider aliases, per-region state, failover strategies), while delegating shared risk classification, version guards, and rollback contract to `terraform-risk-playbook`. Invoked when the user asks to write Terraform, set up infrastructure as code, or review IaC.
Creates or updates AWS-oriented Terraform module structure and implementation scaffolding. Focuses on file layout, variable/output contracts, provider and version constraints, tagging standards, safe composition patterns, and address-stability guardrails.
Designs AWS-targeted Terraform infrastructure plans before implementation. Focuses on service selection, module boundaries, state/backends, environment separation, security/compliance guardrails, acceptance criteria, and explicit risk/validation assumptions.
Diagnoses Terraform/OpenTofu risk before generating changes. Defines the response contract, failure-mode routing, version/runtime guards, validation commands, and rollback expectations for modules, tests, CI, and state work.
Uses lightweight AWS stack emulation for faster local Terraform iteration. Defines what can be safely validated locally, compatibility caveats, and the handoff boundary to real-AWS verification and reviewed plan/apply flows.
Architecture-focused code review covering hexagonal boundary violations, DDD anti-patterns, CQRS misuse, and microservices coupling issues. Applied in addition to the language-specific review skill when architecture markers are detected. Invoked when reviewing hexagonal architectures, DDD patterns, or microservices boundaries.
| name | create-terraform-tests |
| description | Designs and implements Terraform module tests for AWS-targeted modules. Covers terraform-native tests, validation gates, fixture composition, and risk-focused assertions for regressions, address migration, and unsafe changes. |
| version | 1.1.0 |
| tags | ["devops","terraform","testing","aws"] |
| resources | ["tftest-patterns.md"] |
| vendor_support | {"claude":"native","opencode":"native","copilot":"prompt-inject","codex":"prompt-inject","gemini":"prompt-inject"} |
Author Terraform test coverage for AWS modules.
Always pair this skill with terraform-risk-playbook. That skill is
authoritative for the response contract, risk classification, version/runtime
guards, validation chain, and rollback notes.
Authoritative precedence: when this skill and terraform-infrastructure are both
active, this skill is authoritative for module testing strategy, test layout,
and assertion patterns.
Prioritize tests for:
count/for_each, moved flows)Use tftest-patterns.md for baseline structure and pattern selection.
Minimum coverage:
command = apply when assertions depend on computed values or set-type
nested blocksEnsure deterministic checks in CI:
terraform fmt -check -recursiveterraform init -backend=falseterraform validateterraform testCI safety guardrails:
Use minimal fixtures and avoid long-running integration behavior unless explicitly requested. Document emulator vs real-AWS assumptions clearly.
Summarize what is covered, known blind spots, and next highest-value tests. Call out whether each scenario is plan-only confidence, emulator confidence, or real-cloud confidence.