Lean body that assumes Claude's competence: prefix schemes and anti-patterns are condensed into tables, no generic explanations of what a database or migration is, and every section earns its place.

Provides copy-paste-ready executable commands ('docker run --rm flyway/flyway ... migrate', 'brew install flyway'), a concrete flyway.conf block with production guards, and a fully worked end-to-end CI example.

Steps 1-7 are explicitly sequenced as the single source, and the worked example includes a validate->fix feedback loop (checksum mismatch -> add V3 instead of mutating V2); destructive `clean` is explicitly guarded with cleanDisabled=true.

SKILL.md is an overview that defers the full command table and CI job to references/commands.md (a real, one-level-deep file) with clearly signaled markdown links, keeping inline content appropriately scoped.

Lists concrete actions in third person ('Authors and runs Flyway database migrations', 'runs flyway migrate / info / validate / clean / baseline / repair', 'tracks state in the flyway_schema_history table') with concrete file-name examples.

Explicitly answers what it does (author/run migrations, run flyway commands) and when to use it via an explicit 'Use when...' clause with multiple triggers.

The 'Use when the user works with Flyway-managed schemas, asks about migration ordering, or needs CI gates on schema changes' clause covers natural terms a user would say (Flyway, migration ordering, CI gates).

Clearly scoped to Flyway-managed schemas with distinct triggers (flyway commands, flyway_schema_history), unlikely to conflict with the named sister tools (Liquibase, Atlas, SQLMesh).