From terraform-review
This skill should be used when the user asks to "review Terraform code", "Terraform plan review", "check Terraform implementation", "validate infrastructure code", "IaC review", or mentions reviewing Terraform plans, modules, or infrastructure-as-code for production readiness.
npx claudepluginhub sniper-fly/souma-recette --plugin terraform-reviewThis skill uses the workspace's default tool permissions.
This skill provides a structured approach to reviewing Terraform implementation plans before deployment. The focus is on identifying technical issues that should be fixed before implementation begins, with emphasis on production stability and minimizing operational burden.
Reviews Terraform PRs with 8-category checklist on structure, state safety, security, naming, modules, variables, providers, and CI/CD. Outputs Approved/Needs Changes/Blocked verdict for PR reviews, pre-merge checks, and audits.
Audits Terraform codebases for security, compliance, cost optimization, code quality, and architecture issues in AWS resources. Outputs Markdown reports with severity levels, remediations, and HCL fixes.
Validates, lints, audits, and plans Terraform HCL files using tflint, checkov, terraform validate/fmt/init; enforces security checklists and best practices.
Share bugs, ideas, or general feedback.
This skill provides a structured approach to reviewing Terraform implementation plans before deployment. The focus is on identifying technical issues that should be fixed before implementation begins, with emphasis on production stability and minimizing operational burden.
Before reviewing, identify applicable review perspectives based on the plan content. Common perspectives include:
| Category | Focus Areas |
|---|---|
| Resource Design | Dependencies, configuration consistency, lifecycle management |
| Security | IAM permissions, network settings, secrets management |
| Operations | Naming conventions, tagging, module structure, state management |
| Cost | Resource sizing, unused resources, cost optimization options |
| Constraints/Risks | Service limits, quotas, region dependencies |
Adapt perspectives based on the specific plan. Add domain-specific perspectives as needed (e.g., compliance for regulated industries).
Examine the plan against each perspective. For categories with no issues, document as "Confirmed - No issues found."
Use the standard output format for each issue found.
For each issue discovered:
### Issue N: [Issue Title]
- **Location**: Filename/Section, specific configuration item
- **Problem**: What is wrong, why it's a problem
- **Severity**: High/Medium/Low
- High: Deployment failure, security vulnerability, data loss risk
- Medium: Operational difficulty, scalability constraints, maintainability issues
- Low: Best practice deviation, readability concerns
- **Recommendation**: Suggested fix (include code example if applicable)
Conclude with a summary:
---
**Summary**: X issues found
- High: N
- Medium: N
- Low: N
For comprehensive review criteria and checklists, see:
references/review-perspectives.md - Detailed review criteria per categoryFor a complete review example, see:
examples/sample-review-output.md - Sample Terraform review output* wildcards)