review-infrastructure

Review infrastructure-as-code files for security, reliability, and best practice gaps.

9|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/paultyng/skill-issue --skill review-infrastructure-paultyng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-infrastructure
Source: https://github.com/paultyng/skill-issue/tree/main/skills/review-infrastructure
Command: npx skills add https://github.com/paultyng/skill-issue --skill review-infrastructure-paultyng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Infrastructure-as-code and cloud-native configuration reviews are often ad-hoc and inconsistent, leading to missed critical security, reliability, and cost issues across Terraform, Kubernetes, Docker, Helm, gateways, and service meshes. This Skill standardizes the review process to ensure common misconfigurations are caught early, reducing production risk and technical debt.

Core Features & Use Cases

  • Multi-surface coverage: Reviews Terraform/OpenTofu, Kubernetes manifests, Dockerfiles, Helm charts, north-south gateways (Envoy, Ingress, Gateway API), and east-west service meshes (Linkerd, Istio) in a single unified workflow.
  • Integrated static analysis: Runs industry-standard linters and security scanners (tflint, tfsec, kubeconform, hadolint, etc.) when available, and interprets their output in context to avoid false positives.
  • PR and follow-up support: Links findings directly to GitHub PR file lines for easy tracking, and supports re-evaluation of prior findings against updated code in follow-up reviews.
  • Use Case: A team preparing a Kubernetes service deployment can run this review to catch missing resource limits, insecure security contexts, unauthenticated gateway routes, and misconfigured service mesh policies before they reach production.

Quick Start

Use the review-infrastructure skill to review all infrastructure-as-code files in the current repository for security, reliability, and best practice gaps.

Frequently Asked Questions about review-infrastructure

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review Terraform and Kubernetes manifests for misconfigurations?

Reviewing Terraform and Kubernetes manifests requires running integrated static analysis tools like tflint and kubeconform, then interpreting their output in context to prioritize security and reliability findings linked directly to code lines.

What is the best way to catch security issues in Helm charts and Dockerfiles?

Catching security issues in Helm charts and Dockerfiles involves applying unified infrastructure-as-code reviews that run industry-standard linters like hadolint, prioritizing findings to reduce production risk and technical debt before deployment.

Does this infrastructure review process support Envoy gateways and Istio service meshes?

Yes, this infrastructure review process supports Envoy, Ingress, and Gateway API north-south configurations, as well as east-west service mesh setups like Istio and Linkerd, evaluating them for insecure routes and misconfigured policies.

Can I re-evaluate prior infrastructure-as-code review findings on an updated GitHub PR?

Yes, you can re-evaluate prior infrastructure-as-code review findings against updated code in follow-up reviews, linking new prioritized findings directly to GitHub PR file lines for easy tracking and resolution.

How do I avoid false positives when scanning cloud-native infrastructure configurations?

Avoiding false positives when scanning cloud-native infrastructure configurations requires interpreting static analysis tool output in context, applying structured reviews that validate findings against actual Terraform, Kubernetes, and service mesh codebase scopes.