Use when you need to add or review Flyway database migrations in a Micronaut application — micronaut-flyway, db/migration scripts, flyway.datasources.* configuration, and alignment with JDBC or Micronaut Data. This should trigger for requests such as Add or review Flyway migrations in a Micronaut project; Configure micronaut-flyway or db/migration layout; Add versioned Flyway SQL migrations for Micronaut; Review Micronaut database migration ordering; Configure Flyway datasources in a Micronaut p
NewMaintained
Automatic
◆Coding pack
Last verified 8/20/2026
What it changes
Passed 12 of 16 test cases with the skill, and 14 of 16 without it.
Without skill86%
With skill73%
Checks it passed that the model alone missed
Requires human review prior to dropping the table.
Copies existing column data to the new column during migrate phase.
2 fixed14 passed either way1 still failing5 broke
Pass-rate lift
-14 pp
Tokens
+25%
Agent turns
0%
Response time
-17%
Model gemini-3.6-flashMeasured 8/20/2026v116 of 22 cases passed with skill · 16 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 2
Prompt
We need to remove a deprecated table `legacy_logs` from our production PostgreSQL database managed by Micronaut Flyway. What risk assessment must be performed before executing `DROP TABLE legacy_logs;` in a Flyway script?
What was checked, without and with the skill
Checked
Without skill
With skill
Requires human review prior to dropping the table.
Missed
Passed
Assesses whether active application versions rely on the table before dropping it.
Passed
Passed
case-22 · gemini-3.6-flash · 8/20/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md61 lines4 files
Micronaut — Database migrations (Flyway)
Apply Flyway migration guidelines for Micronaut.
What is covered in this Skill?
micronaut-flyway with JDBC/Hikari and database drivers
Versioned SQL under src/main/resources/db/migration
flyway.datasources.* (per-datasource) configuration in YAML/properties
Tests with Testcontainers and real migration chains
Parallel Change as the safe expand, migrate, contract workflow for breaking or data-sensitive schema changes
Coordination with @511-frameworks-micronaut-jdbc and @512-frameworks-micronaut-data
Scope: Apply recommendations based on the reference rules and good/bad examples.
Constraints
Before applying Flyway or SQL changes, ensure the project compiles. After improvements, run full verification.
MANDATORY: Run ./mvnw compile or mvn compile before applying any change
SAFETY: If compilation fails, stop immediately
VERIFY: Run ./mvnw clean verify or mvn clean verify after applying improvements
BEFORE APPLYING: Read the reference for detailed rules and good/bad patterns
BREAKING CHANGE REVIEW: Before recommending or applying a migration, assess whether it can break deployed application versions, dependent services, reports, jobs, or production data interpretation; if yes, require explicit human review before proceeding
EDGE CASE: If the user goal is ambiguous, stop and ask a clarifying question before editing files or running project-wide commands
EDGE CASE: If required context, files, credentials, or tools are missing, report the blocker explicitly and ask whether to proceed with setup or fallback guidance
EDGE CASE: If requested changes conflict with project constraints or safety boundaries, explain the conflict and ask for user confirmation on the preferred trade-off
When to use this skill
Add or review Flyway migrations in a Micronaut project
Configure micronaut-flyway or db/migration layout
Add versioned Flyway SQL migrations for Micronaut
Review Micronaut database migration ordering
Configure Flyway datasources in a Micronaut project
Use when you need to write unit tests for Micronaut applications — Mockito-first with @ExtendWith(MockitoExtension.class), @MicronautTest with @MockBean, HttpClient @Client(/) assertions, @Property overrides, @ParameterizedTest, and *Test vs *IT naming. For framework-agnostic Java use @131-java-testing-unit-testing. This should trigger for requests such as Add or improve unit tests in a Micronaut project; Reduce unnecessary @MicronautTest usage with Mockito-first tests; Write Mockito-first unit