Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →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
.claude/skills/jabrena-416-frameworks-quarkus-mongodb-migrations-mongock/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-09 | ✗→✓ | ▲ Improved | 9% | 0% |
| case-13 | ✗→✓ | ▲ Improved | 6% | 0% |
| case-15 | ✗→✓ | ▲ Improved | 22% | 0% |
| case-21 | ✗→✓ | ▲ Improved | 17% | 0% |
| case-24 | ✗→✓ | ▲ Improved | -36% | 0% |
Apply Mongock migration guidelines for Quarkus and Quarkus MongoDB client/Panache Mongo.
What is covered in this Skill?
quarkus-mongock extension and Quarkus MongoDB client setupquarkus.mongock.* configuration, including migrate-at-start@ChangeUnit migrations with @Execution and rollback hooks@415-frameworks-quarkus-mongodbScope: Apply recommendations based on the reference rules and good/bad examples.
Compile before Mongock or MongoDB migration changes; verify after changes.
./mvnw compile or mvn compile before applying any change./mvnw clean verify or mvn clean verify after applying improvementsquarkus-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.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.
Verify the Quarkiverse quarkus-mongock release and Quarkus extension catalog compatibility before configuring MongoDB connection settings, migration scan behavior, and startup vs explicit MongockFactory execution.
Implement/refactor @ChangeUnit classes with idempotent operations, explicit ordering, rollback hooks, and safe lock/transaction settings.
Execute build/tests, including Quarkus tests with Dev Services or Testcontainers MongoDB where feasible, and summarize outcomes and follow-up risks.
For detailed guidance, examples, and constraints, see:
| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-01 | fail→fail | 15,213 | 6,736 | -56% | 1 | 1 | 0% | 3,002 | 1,322 | -56% | 0 | 0 | — |
case-02 | fail→fail | 4,531 | 6,371 | +41% | 1 | 1 | 0% | 217 | 1,230 | +467% | 0 | 0 | — |
case-03 | fail→fail | 19,284 | 5,881 | -70% | 1 | 1 | 0% | 3,427 | 1,140 | -67% | 0 | 0 | — |
case-04 | pass→pass | 8,270 | 9,142 | +11% | 1 | 1 | 0% | 1,580 | 2,485 | +57% | 0 | 0 | — |
case-05 | pass→pass | 14,639 | 15,781 | +8% | 1 | 1 | 0% | 2,775 | 3,045 | +10% | 0 | 0 | — |
case-06 | pass→pass | 9,424 | 7,320 | -22% | 1 | 1 | 0% | 1,750 | 2,045 | +17% | 0 | 0 | — |
case-07 | pass→pass | 10,275 | 3,530 | -66% | 1 | 1 | 0% | 1,540 | 1,337 | -13% | 0 | 0 | — |
case-08 | fail→fail | 15,361 | 12,254 | -20% | 1 | 1 | 0% | 2,504 | 2,841 | +13% | 0 | 0 | — |
case-09 | fail→pass | 13,800 | 9,373 | -32% | 1 | 1 | 0% | 1,948 | 2,118 | +9% | 0 | 0 | — |
case-10 | pass→pass | 10,996 | 7,614 | -31% | 1 | 1 | 0% | 1,806 | 2,140 | +18% | 0 | 0 | — |
case-11 | pass→pass | 14,099 | 11,577 | -18% | 1 | 1 | 0% | 2,454 | 2,819 | +15% | 0 | 0 | — |
case-12 | pass→pass | 5,851 | 1,762 | -70% | 1 | 1 | 0% | 817 | 1,075 | +32% | 0 | 0 | — |
case-13 | fail→pass | 7,707 | 3,496 | -55% | 1 | 1 | 0% | 1,263 | 1,342 | +6% | 0 | 0 | — |
case-14 | pass→pass | 8,636 | 2,029 | -77% | 1 | 1 | 0% | 1,217 | 1,077 | -12% | 0 | 0 | — |
case-15 | fail→pass | 7,068 | 3,618 | -49% | 1 | 1 | 0% | 1,094 | 1,335 | +22% | 0 | 0 | — |
case-16 | pass→pass | 12,949 | 8,859 | -32% | 1 | 1 | 0% | 2,027 | 2,238 | +10% | 0 | 0 | — |
case-17 | pass→pass | 14,958 | 9,410 | -37% | 1 | 1 | 0% | 2,406 | 2,384 | -1% | 0 | 0 | — |
case-18 | pass→pass | 16,299 | 14,367 | -12% | 1 | 1 | 0% | 2,758 | 3,326 | +21% | 0 | 0 | — |
case-19 | pass→pass | 8,193 | 7,444 | -9% | 1 | 1 | 0% | 1,566 | 2,214 | +41% | 0 | 0 | — |
case-20 | pass→pass | 3,766 | 2,651 | -30% | 1 | 1 | 0% | 696 | 1,229 | +77% | 0 | 0 | — |
case-21 | fail→pass | 7,408 | 4,075 | -45% | 1 | 1 | 0% | 1,257 | 1,476 | +17% | 0 | 0 | — |
case-22 | pass→pass | 6,452 | 1,770 | -73% | 1 | 1 | 0% | 915 | 1,009 | +10% | 0 | 0 | — |
case-23 | pass→pass | 15,502 | 11,583 | -25% | 1 | 1 | 0% | 2,468 | 2,727 | +10% | 0 | 0 | — |
case-24 | fail→pass | 14,340 | 3,752 | -74% | 1 | 1 | 0% | 2,102 | 1,349 | -36% | 0 | 0 | — |
case-25 | pass→pass | 11,712 | 4,790 | -59% | 1 | 1 | 0% | 1,769 | 1,522 | -14% | 0 | 0 | — |
DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 25 cases were attempted, and 22 counted toward the lift figure. The other 3 produced results that are not comparable between the two arms, so they are excluded from the headline rather than averaged into it. The headline lift of +20 percentage points is the difference between those two pass rates over the 22 comparable cases. 1 case got worse with the skill loaded, and it is included in that figure.
Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.
Other measured skills in the registry, with their headline benchmark lift.