Use when you need to add or review Flyway database migrations in a Quarkus application — quarkus-flyway extension, db/migration scripts, quarkus.flyway.* configuration, migrate-at-start, and alignment with JDBC or Panache. This should trigger for requests such as Add or review Flyway migrations in a Quarkus project; Configure quarkus-flyway or db/migration layout; Add versioned Flyway SQL migrations for Quarkus; Review Quarkus database migration ordering; Configure Flyway clean migrate or baseli
NewMaintained
Automatic
◆Coding pack
Last verified 8/21/2026
What it changes
Passed 10 of 16 test cases with the skill, and 10 of 16 without it.
Without skill64%
With skill64%
Checks it passed that the model alone missed
Asks for user confirmation on trade-offs before enabling destructive configuration.
Notes that automatic ORM schema generation is distinct from versioned SQL migration workflows.
2 fixed12 passed either way6 still failing2 broke
Pass-rate lift
0 pp
Tokens
+44%
Agent turns
0%
Response time
-11%
Model gemini-3.6-flashMeasured 8/21/2026v114 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
In our Quarkus dev environment, we want Hibernate ORM to automatically create and update the database schema on launch using JPA entity mappings without migration tools. How should we configure quarkus.hibernate-orm.database.generation?
What was checked, without and with the skill
Checked
Without skill
With skill
Answers the Hibernate ORM schema generation question directly using quarkus.hibernate-orm.database.generation configuration options.
Passed
Passed
Notes that automatic ORM schema generation is distinct from versioned SQL migration workflows.
Missed
Passed
case-05 · gemini-3.6-flash · 8/21/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md61 lines4 files
Quarkus — Database migrations (Flyway)
Apply Flyway migration guidelines for Quarkus.
What is covered in this Skill?
quarkus-flyway with quarkus-jdbc-* drivers
Versioned SQL under src/main/resources/db/migration
Parallel Change as the safe expand, migrate, contract workflow for breaking or data-sensitive schema changes
Coordination with @411-frameworks-quarkus-jdbc and @412-frameworks-quarkus-panache
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 Quarkus project
Configure quarkus-flyway or db/migration layout
Add versioned Flyway SQL migrations for Quarkus
Review Quarkus database migration ordering
Configure Flyway clean migrate or baselines in Quarkus
Use when you need to write fast unit tests for Quarkus applications — including pure tests with @ExtendWith(MockitoExtension.class), @QuarkusTest with @InjectMock for full CDI mock replacement, @InjectSpy for partial CDI bean mocking, REST Assured for resource-focused tests, @ParameterizedTest with @CsvSource / @MethodSource, QuarkusTestProfile for test-specific configuration overrides, and naming conventions (*Test → Surefire, *IT → Failsafe). For framework-agnostic Java use @131-java-testing-u