infra-safe-change

Enforce review and safety checks for Terraform, CloudFormation, and CDK infrastructure changes.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/lgerard314/global-plugin --skill infra-safe-change
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: infra-safe-change
Source: https://github.com/lgerard314/global-plugin/tree/main/plugin/skills/infra-safe-change
Command: npx skills add https://github.com/lgerard314/global-plugin --skill infra-safe-change

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Protect infrastructure changes from unsafe deployments.

Core Features & Use Cases

  • Enforces IaC change reviews across Terraform, CloudFormation, CDK, and other IaC tooling to prevent destructive plans, drift, and risky IAM or networking changes.
  • Provides a structured safety rubric and drift-detection guidance to align live infrastructure with code.
  • Promotes safe deployment practices with required justification and remote-state discipline.

Quick Start

Review the latest Terraform plan and ensure a remote-state backend with locking is configured before applying.

Frequently Asked Questions about infra-safe-change

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

FAQPage Schema
How do I prevent destructive Terraform plan deployments and enforce safe IaC changes?

To prevent destructive Terraform plan deployments, enforce safe IaC changes by requiring documented justification, a remote-state backend with locking, and formal review checks before applying any infrastructure modifications.

What is infrastructure drift detection and how does it align live infrastructure with IaC code?

Infrastructure drift detection identifies configuration differences between live cloud resources and your IaC code, applying a structured safety rubric to ensure your Terraform, CloudFormation, or CDK deployments remain aligned with their documented state.

Does this IaC review process work with CloudFormation and CDK, or only Terraform?

This IaC review process works across Terraform, CloudFormation, CDK, and other IaC tooling, applying consistent guardrails to prevent risky IAM or networking changes regardless of the specific infrastructure deployment framework used.

How do I review risky IAM and networking changes before applying an infrastructure plan?

Review risky IAM and networking changes by applying a structured safety rubric that requires documented justification for modifications, verifies remote-state backend locking, and enforces formal review checks before applying any IaC plan.

Why do I need a remote-state backend with locking to apply safe infrastructure changes?

A remote-state backend with locking is required for safe infrastructure changes because it prevents concurrent modifications, enforces state discipline, and provides the formal review checks necessary to prevent destructive IaC deployments and drift.

What are the limitations of applying infrastructure changes without formal IaC review checks?

Without formal IaC review checks, infrastructure changes risk destructive deployments, unmanaged drift, and risky IAM or networking modifications due to the absence of required justification and remote-state backend locking enforcement.