schema-drift-detector

Name: schema-drift-detector
Availability: InStock
Author: praburajasekaran

Compare schema.rb changes against migrations to detect unrelated modifications in pull requests.

Updated Feb 16, 2026

Search Tags:#code quality #database #drift detection #schema #PR review

Ready to run

npx skills add https://github.com/praburajasekaran/ruthva-clinic-os --skill schema-drift-detector-praburajasekaran

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: schema-drift-detector
Source: https://github.com/praburajasekaran/ruthva-clinic-os/tree/main/.gemini/skills/schema-drift-detector
Command: npx skills add https://github.com/praburajasekaran/ruthva-clinic-os --skill schema-drift-detector-praburajasekaran

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, rails, and includes scripts (resource) components.

What problem does it solve?

Prevents accidental inclusion of unrelated schema.rb changes in Pull Requests (PRs), avoiding merge conflicts and confusion.

Core Features & Use Cases

Detects Unrelated Schema Changes: Cross-references schema.rb against migrations to identify changes that are not part of the PR.
Prevents Merge Conflicts: Helps maintain a clean database schema by catching drift early.
Use Case: Run the schema-drift-detector before reviewing a PR with database schema changes to ensure all changes are related to the PR.

Quick Start

Run 'schema-drift-detector' to check the PR for unrelated schema changes.

Frequently Asked Questions about schema-drift-detector

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

FAQPage Schema

How do I detect unrelated database schema changes in a Pull Request?▼

This tool cross-references schema.rb against included migrations to identify unrelated database schema changes in a Pull Request. It prevents accidental inclusions that cause merge conflicts and confusion.

Why does my Rails Pull Request include unrelated schema.rb modifications?▼

Unrelated schema.rb modifications occur when local database updates are committed without corresponding migrations. A drift detector cross-references these files to catch the issue before review.

Does schema drift detection work with Git and Rails?▼

Yes, schema drift detection requires both Git and Ruby on Rails to access repository state and verify database schema integrity. It compares schema changes against migrations during the code review process.

What is the best way to prevent merge conflicts caused by schema.rb drift?▼

The best way to prevent merge conflicts from schema.rb drift is to verify database schema integrity before reviewing Pull Requests. Catching drift early maintains a clean database schema.

When do I need to run a schema drift detector for code review?▼

You need to run a schema drift detector for code review whenever a Pull Request involves database schema modifications. It ensures all schema.rb changes are directly related to the PR's included migrations.