schema-drift-detector

Detect unrelated schema.rb changes by cross-referencing the PR's database migrations against the schema.rb diff. This validates that schema modifications align with included migrations and surfaces drift indicators during code review.

Schema.rb drift occurs when developers commit unrelated database schema changes alongside feature branch migrations. Cross-referencing the PR diff against included migrations identifies and prevents these unintended schema modifications from leaking into the main branch.

The best way to review database schema changes is to apply a drift check that validates schema.rb modifications against the PR's migrations. This surfaces drift indicators and enforces correct migration workflows during code review.

Enforce a drift-review workflow by validating that schema.rb changes in the PR diff correspond to included migrations. This surfaces drift indicators and provides remediation guidance to ensure correct database migrations.

Yes, you can check schema.rb alignment across feature branches by applying the drift detector during code reviews. It validates that schema.rb changes in each PR diff align with that PR's specific database migrations.

Automated schema drift detection is not suitable when a PR intentionally modifies schema.rb without corresponding database migrations, as the tool cross-references migrations to validate schema changes and flag drift indicators.