413-frameworks-quarkus-db-migrations-flyway
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 baselines in Quarkus. Part of Plinth Toolkit
- Installs
- 315
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/jabrena/plinth --skill 413-frameworks-quarkus-db-migrations-flyway- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads 413-frameworks-quarkus-db-migrations-flyway automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Quarkus — Database migrations (Flyway)
Apply Flyway migration guidelines for Quarkus.
What is covered in this Skill?
quarkus-flywaywithquarkus-jdbc-*drivers- Versioned SQL under
src/main/resources/db/migration quarkus.flyway.migrate-at-start, locations, baseline options- Multiple datasources (when applicable)
- Parallel Change as the safe expand, migrate, contract workflow for breaking or data-sensitive schema changes
- Coordination with
@411-frameworks-quarkus-jdbcand@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 compileormvn compilebefore applying any change - SAFETY: If compilation fails, stop immediately
- VERIFY: Run
./mvnw clean verifyormvn clean verifyafter 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
Workflow
- Read references and assess project context
Read references/413-frameworks-quarkus-db-migrations-flyway.md, references/413-frameworks-quarkus-db-migrations-flyway-antipatterns.md, and references/413-frameworks-quarkus-db-migrations-flyway-parallel-change.md, then inspect the current project setup before proposing changes.
- Gather scope and decide target improvements
Identify requested outcomes, constraints, and the minimum safe set of changes to apply.
- Apply framework-aligned changes
Implement or refactor configuration/code following the reference patterns and project conventions. Use Parallel Change (expand, migrate, contract) as the safe default for breaking or data-sensitive schema changes.
- Run verification and report results
Execute appropriate build/tests and summarize what changed, what was verified, and any follow-up actions.
Reference
For detailed guidance, examples, and constraints, see:
- references/413-frameworks-quarkus-db-migrations-flyway.md
- references/413-frameworks-quarkus-db-migrations-flyway-antipatterns.md
- references/413-frameworks-quarkus-db-migrations-flyway-parallel-change.md
FAQ
What does the 413-frameworks-quarkus-db-migrations-flyway skill do?
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 baselines in Quarkus. Part of Plinth Toolkit
How do I install 413-frameworks-quarkus-db-migrations-flyway?
Run npx skills add https://github.com/jabrena/plinth --skill 413-frameworks-quarkus-db-migrations-flyway in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/413-frameworks-quarkus-db-migrations-flyway/ (personal) or .claude/skills/413-frameworks-quarkus-db-migrations-flyway/ (project).
Which AI agents can use 413-frameworks-quarkus-db-migrations-flyway?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is 413-frameworks-quarkus-db-migrations-flyway safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains 413-frameworks-quarkus-db-migrations-flyway?
It is published by jabrena in jabrena/plinth. It has 315 recorded installs.
More from jabrena/plinth
110-java-maven-best-practices
jabrena/plinth
Use when you need to review, improve, or troubleshoot a Maven pom.xml file — including dependency management with BOMs, plugin configuration, version centralization, multi-module project structure, build profiles, or any situation where you want to align your Maven setup with industry best practices. This should trigger for requests such as Review pom.xml to improve it; Apply Maven best practices to pom.xml; Improve Maven POM configuration; Review Maven dependency management and plugin configuration; Modernize Maven build conventions for a Java project. Part of Plinth Toolkit
121-java-object-oriented-design
jabrena/plinth
Use when reviewing, improving, or refactoring Java object-oriented design, including applying SOLID, DRY, or YAGNI; improving classes and interfaces; correcting encapsulation, inheritance, or polymorphism; resolving God Class, Feature Envy, or Data Clumps; and improving object creation, methods, or exception contracts. Triggers include review Java OOD, refactor Java OOD, improve Java OOD, fix OOP misuse, and identify Java code smells. Part of Plinth Toolkit
124-java-secure-coding
jabrena/plinth
Use when you need to apply Java secure coding best practices — including validating untrusted inputs, defending against injection attacks with parameterized queries, minimizing attack surface via least privilege, applying strong cryptographic algorithms, handling exceptions securely without exposing sensitive data, managing secrets at runtime, avoiding unsafe deserialization, and encoding output to prevent XSS. This should trigger for requests such as Review Java code for secure coding; Find input validation risks in Java code; Review Java code for injection vulnerabilities; Improve secure error handling in Java services; Harden Java code against common security flaws. Part of Plinth Toolkit
131-java-testing-unit-testing
jabrena/plinth
Open the skill to read its SKILL.md instructions.
141-java-refactoring-with-modern-features
jabrena/plinth
Open the skill to read its SKILL.md instructions.
125-java-concurrency
jabrena/plinth
Open the skill to read its SKILL.md instructions.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.