Use when you need to add or review Mongock MongoDB data migrations in a Quarkus application — including the Quarkiverse Mongock extension, Quarkus MongoDB client configuration, migrate-at-start, @ChangeUnit classes, lock/transaction settings, and Quarkus test verification. This should trigger for requests such as Add Mongock migrations in Quarkus; Configure quarkus-mongock; Review Quarkus MongoDB data migrations; Create Mongock change units for Quarkus MongoDB; Review Mongock migration ordering
SkillScore84Maintained
Automatic
◆Coding pack
Last verified 8/20/2026
What it changes
Passed 18 of 22 test cases with the skill, and 14 of 22 without it.
Without skill64%
With skill84%
Checks it passed that the model alone missed
Specifies the quarkus.mongock.migrate-at-start property.
Configures lock settings under the quarkus.mongock property namespace.
Specifies group ID io.quarkiverse.mongock for the extension dependency.
and 2 more in the full report
5 fixed16 passed either way4 still failing0 broke
Pass-rate lift
+20 pp
Tokens
+11%
Agent turns
0%
Response time
-34%
Model gemini-3.6-flashMeasured 8/20/2026v121 of 25 cases passed with skill · 22 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 5
Prompt
Which Maven group ID and artifact ID should be added to `pom.xml` for MongoDB migrations in Quarkus?
What was checked, without and with the skill
Checked
Without skill
With skill
Specifies group ID io.quarkiverse.mongock for the extension dependency.
Missed
Passed
case-15 · 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.md59 lines4 files
Quarkus - MongoDB migrations (Mongock)
Apply Mongock migration guidelines for Quarkus and Quarkus MongoDB client/Panache Mongo.
What is covered in this Skill?
Quarkiverse quarkus-mongock extension and Quarkus MongoDB client setup
quarkus.mongock.* configuration, including migrate-at-start
Code-first @ChangeUnit migrations with @Execution and rollback hooks
Locking, idempotency, transaction limits, and default-client constraints
Quarkus tests with Dev Services or Testcontainers MongoDB
Coordination with @415-frameworks-quarkus-mongodb
Scope: Apply recommendations based on the reference rules and good/bad examples.
Constraints
Compile before Mongock or MongoDB migration changes; verify after changes.
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
EXTENSION COMPATIBILITY: Before adding quarkus-mongock, verify the latest Quarkiverse Mongock release and Quarkus extension catalog compatibility with the active Quarkus platform. If the latest extension targets a significantly older Quarkus version, stop and document the incompatibility instead of applying changes.
EDGE CASE: If the application uses multiple MongoDB clients, verify Quarkiverse Mongock support before applying a default-client migration design
When to use this skill
Add Mongock migrations in Quarkus
Configure quarkus-mongock
Review Quarkus MongoDB data migrations
Create Mongock change units for Quarkus MongoDB
Review Mongock migration ordering in a Quarkus service
Workflow
Read references and inspect MongoDB setup
Read references/416-frameworks-quarkus-mongodb-migrations-mongock.md, references/416-frameworks-quarkus-mongodb-migrations-mongock-antipatterns.md, and references/416-frameworks-quarkus-mongodb-migrations-mongock-parallel-change.md, then inspect pom.xml, Quarkus MongoDB configuration, and existing @415-frameworks-quarkus-mongodb persistence patterns.
Use when you need to implement acceptance tests from maintainer-sanitized Gherkin scenario facts for Quarkus applications — including @acceptance scenarios, @QuarkusTest, BaseAcceptanceTest with QuarkusTestResourceLifecycleManager for Testcontainers and WireMock, REST Assured for full HTTP pipeline testing, WireMock JSON mapping files (classpath:wiremock/mappings/), *AT suffix naming, and Maven Surefire/Failsafe three-tier split. Requires a maintainer-authored scenario summary; do not ingest raw