What problem does it solve? Infrastructure code decides what can go wrong in production, yet it is often reviewed less than application code. This Skill reads a repository's Terraform, Kubernetes, Helm, Docker, compose, devcontainer, and other IaC files to answer what environment could be rebuilt from the repo alone, what is missing, and where the declared infrastructure is weaker than the application it hosts. ## Core Features & Use Cases - IaC inventory and coverage: Classifies every infrastructure file by tool, counts declared resources, and states honestly what the runtime environment needs that nothing declares — including infrastructure CI mutates by name but the repo never defines. - Hardening review: Judges image pinning, root users, privileged containers, exposed ports, public access, resource limits, and build-secret surfaces with calibrated severity levels. - Environment and state analysis: Maps how staging differs from production, where Terraform state lives, and whether the apply path is a pipeline, manual, or absent. - Use Case: Point it at a repository with Dockerfiles and a Kubernetes deploy directory to receive a structured findings report covering workloads, ingress, environment variants, and a posture summary of what could be rebuilt from the repo. ## Quick Start Ask the AI to run an IaC scan on this repository and report what infrastructure is declared, what is missing, and any hardening risks.
