513-frameworks-micronaut-db-migrations-flyway — Claude Code skill
The 513-frameworks-micronaut-db-migrations-flyway skill guides Flyway migration work in Micronaut, covering SQL files, datasource settings, migration order, tests, and schema-change safety.
Apache-2.0 317 installs ★ 465 updated 2026-10-21
npx skills add jabrena/plinth --skill 513-frameworks-micronaut-db-migrations-flyway -a claude-codeWhat 513-frameworks-micronaut-db-migrations-flyway does
The skill covers micronaut-flyway, JDBC/Hikari, database drivers, and versioned SQL files stored under src/main/resources/db/migration. It also guides flyway.datasources.* settings for separate datasources and checks alignment with JDBC or Micronaut Data.
Its workflow includes real migration-chain tests with Testcontainers and the Parallel Change pattern: expand, migrate, contract. The agent reads the reference files, inspects the project, then selects the smallest safe set of edits.
A failed ./mvnw compile or mvn compile stops the work before changes are applied. After improvements, verification uses ./mvnw clean verify or mvn clean verify. Changes that could break deployed versions or data interpretation require explicit human review.
What it helps with
- add a versioned SQL migration to a Micronaut app
- configure
micronaut-flywayandflyway.datasources.* - check the order of Flyway migrations
- test a real migration chain with Testcontainers
- split a risky schema change into expand, migrate, and contract
Example prompts for the agent
- Add a Flyway migration for a new table in this Micronaut project.
- Review the SQL order under
src/main/resources/db/migrationand checkflyway.datasources.*. - Assess this schema change and design a safe expand, migrate, and contract sequence.
How to install 513-frameworks-micronaut-db-migrations-flyway
1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 513-frameworks-micronaut-db-migrations-flyway -a claude-code2Manually: put the files in place
~/.claude/skills/513-frameworks-micronaut-db-migrations-flyway/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/513-frameworks-micronaut-db-migrations-flyway/
1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 513-frameworks-micronaut-db-migrations-flyway -a codex2Manually: put the files in place
.agents/skills/513-frameworks-micronaut-db-migrations-flyway/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 513-frameworks-micronaut-db-migrations-flyway -a cursor2Manually: put the files in place
.cursor/skills/513-frameworks-micronaut-db-migrations-flyway/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install jabrena/plinth skills/513-frameworks-micronaut-db-migrations-flyway2Manually: put the files in place
.github/skills/513-frameworks-micronaut-db-migrations-flyway/SKILL.md1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 513-frameworks-micronaut-db-migrations-flyway -a gemini-cli2Platform CLI
gemini skills install https://github.com/jabrena/plinth --path skills/513-frameworks-micronaut-db-migrations-flywayManually: put the files in place
.devin/skills/513-frameworks-micronaut-db-migrations-flyway/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 513-frameworks-micronaut-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 513-frameworks-micronaut-db-migrations-flyway
How do I install 513-frameworks-micronaut-db-migrations-flyway in Claude Code?
Run npx skills add jabrena/plinth --skill 513-frameworks-micronaut-db-migrations-flyway -a claude-code, then check ~/.claude/skills/513-frameworks-micronaut-db-migrations-flyway/SKILL.md.
What does 513-frameworks-micronaut-db-migrations-flyway do?
It guides Flyway migration work in Micronaut, including SQL layout, datasource configuration, migration ordering, and migration-chain tests.
What happens when the project does not compile?
The workflow stops after ./mvnw compile or mvn compile fails. Once changes are made, it runs ./mvnw clean verify or mvn clean verify for verification.
Source text
SKILL.md · Apache-2.0
--- name: 513-frameworks-micronaut-db-migrations-flyway description: Use when you need to add or review Flyway database migrations in a Micronaut application — micronaut-flyway, db/migration scripts, flyway.datasources.* configuration, and alignment with JDBC or Micronaut Data. This should trigger for requests such as Add or review Flyway migrations in a Micronaut project; Configure micronaut-flyway or db/migration layout; Add versioned Flyway SQL migrations for Micronaut; Review Micronaut database migration ordering; Configure Flyway datasources in a Micronaut project. Part of Plinth Toolkit license: Apache-2.0 metadata: author: Juan Antonio Breña Moral version: 0.19.0 --- # Micronaut — Database migrations (Flyway) Apply Flyway migration guidelines for Micronaut. **What is covered in this Skill?** - `micronaut-flyway` with JDBC/Hikari and database drivers - Versioned SQL under `src/main/resources/db/migration` - `flyway.datasources.*` (per-datasource) configuration in YAML/properties - Tests with Testcontainers and real migration chains - Parallel Change as the safe expand, migrate, contract workflow for breaking or data-sensitive schema changes - Coordination with `@511-frameworks-micronaut-jdbc` and `@512-frameworks-micronaut-data` **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 Micronaut project - Configure micronaut-flyway or db/migration layout - Add versioned Flyway SQL migrations for Micronaut - Review Micronaut database migration ordering - Configure Flyway datasources in a Micronaut project ## Workflow 1. **Read references and assess project context** Read `references/513-frameworks-micronaut-db-migrations-flyway.md`, `references/513-frameworks-micronaut-db-migrations-flyway-antipatterns.md`, and `references/513-frameworks-micronaut-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/513-frameworks-micronaut-db-migrations-flyway.md](references/513-frameworks-micronaut-db-migrations-flyway.md) - [references/513-frameworks-micronaut-db-migrations-flyway-antipatterns.md](references/513-frameworks-micronaut-db-migrations-flyway-antipatterns.md) - [references/513-frameworks-micronaut-db-migrations-flyway-parallel-change.md](references/513-frameworks-micronaut-db-migrations-flyway-parallel-change.md)
© Juan Antonio Breña Moral · Apache-2.0 · jabrena/plinth