413-frameworks-quarkus-db-migrations-flyway — Claude Code skill
A skill that has your coding agent add and review Flyway migrations in a Quarkus app: the quarkus-flyway extension, SQL scripts, config and ordering.
npx skills add jabrena/plinth --skill 413-frameworks-quarkus-db-migrations-flyway -a claude-codeWhat 413-frameworks-quarkus-db-migrations-flyway does
The skill walks an agent through database migrations in Quarkus. It wires up quarkus-flyway alongside quarkus-jdbc-* drivers, keeps versioned SQL files in src/main/resources/db/migration, and covers settings such as quarkus.flyway.migrate-at-start, locations and baseline options. Multiple datasources get their own pass.
Three references ship with it: the main rules file with good and bad examples, an antipatterns list, and a write-up of Parallel Change — the expand, migrate, contract path for breaking or data-sensitive schema changes. It also coordinates with the neighbouring @411-frameworks-quarkus-jdbc and @412-frameworks-quarkus-panache skills, so migrations stay in step with your data access code.
Before touching anything, the agent must run ./mvnw compile or mvn compile and stop if that fails; afterwards it runs ./mvnw clean verify. If a migration could break deployed app versions, dependent services, reports or jobs, the skill demands an explicit human decision. Worth knowing: it won't quietly apply a risky change, it will ask you first.
What it helps with
- add a versioned SQL migration to a Quarkus project
- configure
quarkus-flywayand thedb/migrationlayout - review migration ordering and baseline settings
- split migrations across multiple datasources
- run a breaking schema change through expand, migrate, contract
Example prompts for the agent
- Add a Flyway migration for a new orders table in this Quarkus project
- Review migration ordering under
src/main/resources/db/migrationand thequarkus.flyway.migrate-at-startsetting - Split the Flyway migrations across two datasources and check the baseline
How to install 413-frameworks-quarkus-db-migrations-flyway
1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 413-frameworks-quarkus-db-migrations-flyway -a claude-code2Manually: put the files in place
~/.claude/skills/413-frameworks-quarkus-db-migrations-flyway/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/413-frameworks-quarkus-db-migrations-flyway/
1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 413-frameworks-quarkus-db-migrations-flyway -a codex2Manually: put the files in place
.agents/skills/413-frameworks-quarkus-db-migrations-flyway/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 413-frameworks-quarkus-db-migrations-flyway -a cursor2Manually: put the files in place
.cursor/skills/413-frameworks-quarkus-db-migrations-flyway/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install jabrena/plinth 413-frameworks-quarkus-db-migrations-flyway2Manually: put the files in place
.github/skills/413-frameworks-quarkus-db-migrations-flyway/SKILL.md1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 413-frameworks-quarkus-db-migrations-flyway -a gemini-cli2Platform CLI
gemini skills install https://github.com/jabrena/plinth --path skills/413-frameworks-quarkus-db-migrations-flywayManually: put the files in place
.devin/skills/413-frameworks-quarkus-db-migrations-flyway/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 413-frameworks-quarkus-db-migrations-flyway -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about 413-frameworks-quarkus-db-migrations-flyway
How do I install 413-frameworks-quarkus-db-migrations-flyway in Claude?
Run npx skills add jabrena/plinth --skill 413-frameworks-quarkus-db-migrations-flyway -a claude-code. The skill lands at ~/.claude/skills/413-frameworks-quarkus-db-migrations-flyway/SKILL.md.
What does this skill do?
It helps an agent add and review Flyway migrations in a Quarkus app: setting up the extension, placing SQL scripts, configuring quarkus.flyway.* options and keeping migration order straight.
Does it need anything before it runs?
It expects a project that compiles. The agent runs ./mvnw compile or mvn compile before any change and stops on failure, then runs ./mvnw clean verify once the work is done.
Source text
SKILL.md · Apache-2.0
--- name: 413-frameworks-quarkus-db-migrations-flyway description: 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 license: Apache-2.0 metadata: author: Juan Antonio Breña Moral version: 0.19.0 --- # 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` - `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-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 ## Workflow 1. **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. 2. **Gather scope and decide target improvements** Identify requested outcomes, constraints, and the minimum safe set of changes to apply. 3. **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. 4. **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.md) - [references/413-frameworks-quarkus-db-migrations-flyway-antipatterns.md](references/413-frameworks-quarkus-db-migrations-flyway-antipatterns.md) - [references/413-frameworks-quarkus-db-migrations-flyway-parallel-change.md](references/413-frameworks-quarkus-db-migrations-flyway-parallel-change.md)
© Juan Antonio Breña Moral · Apache-2.0 · jabrena/plinth