Schema Diff Analyzer Protocol

This skill takes two schema definitions (Source vs Target, or Environment A vs Environment B) and calculates the correct, safe delta between them. It doesn't blindly apply changes; it evaluates risk.

Core assumption: Applying standard ORM or CLI diff outputs directly to production often creates dangerous lock conditions.

0. Context Intake

Before designing, make sure you have the inputs below. Read the previous workflow step's artifact first if it exists. Ask only for what is missing, in a single message, and state any assumption you make instead of blocking.

• The two schemas to compare (environment dumps, migration folders, or declarative definitions).
• Which side is the source of truth.
• Whether the target holds production data.

1. Diff Extraction & Categorization

Analyze the two inputs. Group identified changes into three core risk categories: