schema-drift-detector

Cross-reference schema.rb changes against included migrations to detect drift in pull requests.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/Andreicr1/netz-analysis-engine --skill schema-drift-detector-andreicr1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: schema-drift-detector
Source: https://github.com/Andreicr1/netz-analysis-engine/tree/main/.gemini/skills/schema-drift-detector
Command: npx skills add https://github.com/Andreicr1/netz-analysis-engine --skill schema-drift-detector-andreicr1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects unrelated schema.rb changes in PRs by cross-referencing against included migrations. Use when reviewing PRs with database schema changes.

Core Features & Use Cases

  • Identify schema.rb changes in the PR that lack corresponding migrations.
  • Cross-reference migrations to ensure every schema alteration is backed by a migration.
  • Provide actionable remediation guidance to resolve drift during PR reviews.

Quick Start

Scan a PR against the base branch to identify schema drift in schema.rb and outline required migrations.

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 schema.rb drift in a Rails PR?

Detect schema.rb drift by comparing the PR branch against the base branch to locate schema changes and cross-referencing them against included migrations to highlight unbacked alterations.

What is schema drift in Rails migrations?

Schema drift occurs when schema.rb contains alterations lacking corresponding migrations. Cross-referencing checks identify these drift indicators to enforce safe PR review.

How do I review a PR for unrelated database schema changes?

Review PR schema changes by applying cross-referencing checks to ensure every schema.rb alteration is backed by a corresponding migration, highlighting drift indicators.

What should I do when a migration and schema.rb do not match during code review?

When migration and schema.rb mismatch, resolve drift by following actionable remediation guidance to reset or adjust migrations during PR review.

Can I check for missing migrations in a git diff automatically?

Yes, scan a PR against the base branch to identify schema drift in schema.rb, cross-reference the git diff, and outline required missing migrations.

Does this schema drift detector work without specific dependencies?

Yes, the schema drift detector operates with no dependencies, cross-referencing migrations against schema.rb changes directly from the git diff during PR review.