stack-change-review

Name: stack-change-review
Availability: InStock
Author: PROTOTYP

Review infrastructure configuration changes for safety before merging.

Updated May 7, 2026

Search Tags:#code review #infrastructure #risk assessment #change management #system safety

Ready to run

npx skills add https://github.com/prototypdigital/claude-marketplace --skill stack-change-review

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill unit addresses the issue of merging high-risk infrastructure changes without sufficient review, potentially leading to system instability or downtime.

Core Features & Use Cases

Automated Review Trigger: Detects and flags changes to infrastructure configurations and files across various tools and platforms.
Port and Volume Path Safety Checks: Identifies port number changes, volume path renames or changes, to prevent security breaches and data loss.
Image Tag Analysis: Ensures API compatibility when updating image versions to avoid breaking applications.
Service and Environment Variables Integrity: Flags changes in service names and environment variables to maintain service consistency and avoid misconfigurations.
Runbook Update Requirement: Requires a documented rollback plan for flagged changes to ensure safe rollback in case of issues.

Quick Start

Review infrastructure changes using the stack-change-review skill by merging a commit that alters a critical infrastructure configuration file.

Frequently Asked Questions about stack-change-review

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

FAQPage Schema

How do I review infrastructure changes for safety before merging?▼

To review infrastructure changes for safety, you can trigger an automated review by merging a commit that alters a critical infrastructure configuration file. The review identifies breaking changes in image tags, service names, and environment variables.

What infrastructure files are checked during a configuration review?▼

Infrastructure configuration reviews check files and settings across Docker, Ansible, Kubernetes, Terraform, and environment variables. The process specifically targets port number changes, volume path renames, and image tag updates to prevent security breaches and data loss.

How do I prevent breaking changes when updating Docker image tags?▼

To prevent breaking changes when updating Docker image tags, an automated image tag analysis checks for API compatibility. This ensures updating image versions avoids breaking applications and maintains system stability before the merge.

Can I use automated checks to verify Kubernetes environment variable changes?▼

Yes, you can use automated checks to verify Kubernetes environment variable changes. The review flags changes in service names and environment variables to maintain service consistency and avoid misconfigurations across your infrastructure.

When do I need a rollback plan for infrastructure changes?▼

You need a rollback plan for infrastructure changes when a review flags modifications to ports, volumes, or image tags. A documented runbook update is required as a rollback plan to ensure safe recovery in case of issues.

What is the best way to manage Terraform configuration risks?▼

The best way to manage Terraform configuration risks is through an automated change review that detects high-risk modifications before merging. This prevents system instability by requiring proper rollback procedures for any flagged infrastructure changes.