Schema Evolution Impact Analysis

To analyze database schema impact, this Skill parses your code to trace references to modified models and fields, classifying downstream effects on repositories, services, handlers, and tests as breaking or requiring updates. It verifies migration completeness to prevent unexpected breakages.

Database migration impact analysis identifies all downstream code affected by model or schema modifications. You need it when evolving database structures to ensure necessary updates are made across services, handlers, and tests, preventing unexpected application breakages.

To check migration completeness, this Skill verifies required database migrations and data backfill needs by tracing modified model references throughout your code. It ensures all affected repositories and services are updated to accommodate the schema evolution.

Yes, you can trace affected services and tests by parsing code for references to modified models and fields. This Skill pinpoints all repositories, handlers, and tests needing updates, classifying the impact as breaking or non-breaking based on the schema change.

The best way to find breaking changes is to trace references to the modified model across your entire codebase. This Skill analyzes the impact of schema modifications, pinpointing all services, handlers, and tests that need updates to accommodate the new field.

Modifying a database schema causes unexpected breakages when downstream services, handlers, and tests are not updated to accommodate the changes. This Skill automates impact analysis by classifying code references to modified models as breaking or needing updates.