メニュー
Non-interactive test harness for end-to-end Terraform workflow testing. Runs full `/tf-module-plan` -> `/tf-module-implement` cycle with test defaults, bypassing user prompts for automated validation. Pass the prompt filename as the skill argument.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Internal helper contract for calling the codex-companion runtime from Claude Code
Comprehensive guide for Terraform code style, formatting, and best practices based on HashiCorp's official standards and Azure Verified Modules (AVM) requirements. Use when writing or reviewing Terraform configurations, formatting code, organizing files and modules, establishing team conventions, managing version control, ensuring code quality and consistency across infrastructure projects, or developing Azure Verified Modules.
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
Design engineering for Codex. Build interfaces with craft, memory, and enforcement. Maintains consistent design decisions across sessions - make choices once, enforce them automatically.
Implement plan using concurrent opus agents and verify completion
Deterministic integration test coverage analysis using off-the-shelf tooling. Use this skill whenever the user asks about test coverage, coverage gaps, untested code, what needs testing, or wants to improve integration test coverage. Also trigger when the user says 'run coverage', 'check coverage', 'coverage report', 'what's untested', 'find gaps', or has just implemented a feature and wants to know what integration tests are missing. This skill runs real tools and produces data-driven reports — not guesswork.
| name | tf-module-e2e |
| description | Non-interactive test harness for end-to-end Terraform workflow testing. Runs full `/tf-module-plan` -> `/tf-module-implement` cycle with test defaults, bypassing user prompts for automated validation. Pass the prompt filename as the skill argument. |
| source | image |
Follow /tf-module-plan skill phases with these E2E-specific differences:
Follow /tf-module-implement skill phases (reads module-design.md) with these E2E-specific differences:
After implementation completes, verify:
[x]Display: > E2E module test complete. Status: [PASSED|FAILED]. See issue # for details.