infrastructure-drift-check

Name: infrastructure-drift-check
Availability: InStock
Author: PROTOTYP

Verify infrastructure-as-code consistency with deployed Terraform, Ansible, Kubernetes, and Docker Compose configurations.

Updated May 7, 2026

Search Tags:#IaC #Ansible #Terraform #infrastructure drift #pre-merge verification

Ready to run

npx skills add https://github.com/prototypdigital/claude-marketplace --skill infrastructure-drift-check

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: infrastructure-drift-check
Source: https://github.com/prototypdigital/claude-marketplace/tree/main/llm/skills/infrastructure-drift-check
Command: npx skills add https://github.com/prototypdigital/claude-marketplace --skill infrastructure-drift-check

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the need to confirm that infrastructure-as-code (IaC) declarations align with actual deployed state, reducing the risk of configuration drift during code merges.

Core Features & Use Cases

Pre-Merge Verification: Checks for consistency between IaC files and live infrastructure before code merges.
Cross-Platform Support: Integrates with Terraform, Ansible, Kubernetes, Docker Compose, and more.
Customizable Flags: Flags issues requiring manual review and prevents unintended destructive changes.
Use Case: Before merging a change to your infrastructure code, use this Skill to detect any discrepancies between your IaC and live deployment, preventing deployment errors and ensuring service continuity.

Quick Start

Run the infrastructure-drift-check skill on the latest PR to ensure infrastructure drift is minimized before merging.

Frequently Asked Questions about infrastructure-drift-check

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

FAQPage Schema

How do I check for Terraform configuration drift before merging infrastructure code?▼

Infrastructure drift detection compares your Terraform declarations against live deployed state to identify discrepancies before merging code, preventing unintended destructive changes and deployment errors.

What is infrastructure drift in infrastructure-as-code and how do I prevent it during code merges?▼

Infrastructure drift occurs when deployed infrastructure diverges from declared IaC state. You prevent it by verifying consistency between IaC files and live deployment state prior to merging code changes.

Does infrastructure drift verification work with both Ansible and Kubernetes configurations?▼

Yes, infrastructure drift verification supports cross-platform checks for Ansible, Kubernetes, Docker Compose, and Terraform configurations, ensuring declared infrastructure state aligns with actual deployments across multiple tools.

How do I run a pre-merge verification to detect discrepancies between IaC and live deployment?▼

Run a pre-merge verification on your latest pull request to detect discrepancies between IaC and live deployment. This process flags issues requiring manual review and ensures service continuity before code merges.

Can I customize which infrastructure drift issues require manual review before merging?▼

Yes, you can customize flags for infrastructure drift issues requiring manual review. This prevents unintended destructive changes by ensuring problematic discrepancies are caught and reviewed before code merges.

What configurations do I need to verify infrastructure-as-code consistency with deployment state?▼

You need Terraform, Ansible, Kubernetes, and Docker Compose configurations to verify infrastructure-as-code consistency. The verification checks these declared states against live deployment to minimize infrastructure drift.