coordinate-changes

What problem does it solve?

For multi-file migrations, updates can leave intermediate states that break builds, tests, or downstream integrations. This skill ensures atomic, ordered changes so the repository always transitions from a proven baseline to the next.

Core Features & Use Cases

• Build a dependency order to apply changes from Types → Producers → Consumers → Tests, guaranteeing correct sequencing.
• Validate and enforce that 3+ file changes or shared contracts are applied atomically, preventing partial migrations.
• Provide a batch execution workflow with verification and rollback readiness to minimize disruption during refactors.
• Use across large-scale migrations where safety nets are required to maintain compatibility between producers and consumers.

Quick Start

Identify all target files, determine dependency order, and apply changes atomically in that sequence.