flyway-migration-checker

Validate Flyway SQL migrations for backward compatibility and RGPD compliance.

Updated May 15, 2026
One-click install
npx skills add https://github.com/avgarcia/runcriticon --skill flyway-migration-checker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flyway-migration-checker
Source: https://github.com/avgarcia/runcriticon/tree/main/.claude/skills/flyway-migration-checker
Command: npx skills add https://github.com/avgarcia/runcriticon --skill flyway-migration-checker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents production migration failures by checking Flyway SQL changes against Runcriticon database compatibility, naming, persistence, and RGPD rules before they are merged.

Core Features & Use Cases

  • Migration Validation: Reviews Flyway migration files for backward compatibility, deploy-then-migrate safety, and breaking schema changes.
  • Database Rule Checking: Verifies module schema boundaries, naming conventions, UUID and timestamp usage, constraints, club_id indexes, and event projection requirements.
  • Compliance Checks: Ensures new tables declare RGPD categories and follow retention and deletion policies defined by the project architecture.
  • Use Case: A backend developer can use this Skill during a pull request review to detect unsafe SQL changes before they reach production.

Quick Start

Use the flyway-migration-checker skill to review the migration changes in my current branch and report any blocking compatibility or persistence issues.

Frequently Asked Questions about flyway-migration-checker

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

FAQPage Schema
How do I validate Flyway migrations for backward compatibility before merging?

You validate Flyway migrations by reviewing SQL files for backward compatibility, deploy-then-migrate safety, and breaking schema changes before merge. This Skill checks naming conventions, persistence constraints, and schema isolation rules against defined project standards.

What database schema rules are checked during a Flyway migration review?

Database schema rules checked include module schema boundaries, naming conventions, UUID and timestamp usage, constraints, club_id indexes, and event projection requirements. The review validates these against defined project rules to ensure architectural compliance.

Can I check RGPD compliance in SQL database migrations?

Yes, you can check RGPD compliance by validating that new tables declare RGPD categories and follow retention and deletion policies. This Skill ensures new database tables align with RGPD requirements defined by the project architecture during migration reviews.

Does this migration checker work with deploy-then-migrate workflows?

Yes, it works with deploy-then-migrate workflows by validating SQL changes for backward compatibility and breaking change risks before merge. The review ensures Flyway migrations remain safe within this deployment context by checking schema isolation and persistence constraints.

How do I detect breaking schema changes in SQL migration files?

You detect breaking schema changes by reviewing SQL migration files against backward compatibility, naming, and persistence rules. This Skill identifies unsafe modifications to constraints, schema boundaries, and indexes that could cause production migration failures before merge.