Skip to content
Back to skills

Infrastructure Review

ASecurity

Review Terraform or OpenTofu changes against the intended environment, state, plan, replacement risk, and authorized apply scope.

  • 3 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 13, 2026
ai-agentsterraformgitdatabasebackend

Security analysis

A100/100

Scanned October 13, 2026

npx -y skills add sujith011/agentic-pro-skills --skill infrastructure-review --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Infrastructure Review?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Infrastructure Review
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/sujith011-infrastructure-review/badge)](https://www.skillsdirectory.com/skills/sujith011-infrastructure-review)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: infrastructure-review
description: "Review Terraform or OpenTofu changes against the intended environment, state, plan, replacement risk, and authorized apply scope."
---

# Infrastructure Review

## Process
1. Identify provider/tool versions, lockfile, backend, workspace, account/project, region, and environment. Confirm the target before operations that contact infrastructure.
2. Review configuration and static validation first. Explain whether plan generation refreshes remote state, invokes external data sources, or needs credentials; plan is not always an offline operation.
3. Protect state and plan artifacts as potentially sensitive. Inspect locking, recovery, and concurrent-change behavior for the actual backend.
4. Read the plan for deletes/replacements, address moves, permission changes, public exposure, quotas/cost, and unknown values. A smaller textual diff may still destroy a large resource.
5. Separate code review from apply. If apply is authorized, verify the final plan matches the authorized target and revision, and avoid a stale plan after intervening changes.
6. Define service/data recovery for failures. Reapplying old configuration may not restore destroyed data; record post-apply checks if execution is in scope.

## Example
Renaming a resource address schedules destruction and recreation of a database. Use the tool's supported move/import approach and verify the resulting plan preserves the intended resource identity.

## Stop conditions
Do not force-unlock, rewrite state, or apply changes to escape a mismatch without resolving ownership and authorization. Redacting display output does not remove secrets from stored artifacts.

## Evidence
- Environment/revision and tool/provider versions.
- Reviewed plan effects and sensitive artifact handling.
- Recovery expectations and checks actually executed.

## Reference
Workflow independently written after reviewing [terraform-specialist](https://github.com/sickn33/agentic-awesome-skills/blob/cb30121a2dfd007531bd2fbefb56f68de927da6a/skills/terraform-specialist/SKILL.md).

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.