313 Frameworks Spring Db Migrations Flyway logo

313 Frameworks Spring Db Migrations Flyway

Community
jabrena
313-frameworks-spring-db-migrations-flyway

Use when you need to add or review Flyway database migrations in a Spring Boot application — Maven dependencies, db/migration scripts, spring.flyway.* configuration, baseline and validation, and alignment with JDBC or Spring Data JDBC. This should trigger for requests such as Add or review Flyway migrations in a Spring Boot project; Configure spring.flyway or db/migration layout; Add versioned Flyway SQL migrations for Spring Boot; Review Spring Boot database migration ordering; Fix repeatable Flyway migrations in a Spring project. Part of Plinth Toolkit

Overview

Publisherjabrena
Repositoryplinth
Skill name313-frameworks-spring-db-migrations-flyway
Stars
455
Forks
95
Bundled files
3
LicenseApache-2.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 3 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by jabrena on GitHub. Read the source before you install it.

Installation

Install the 313 Frameworks Spring Db Migrations Flyway AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/jabrena/plinth/tree/main/skills/313-frameworks-spring-db-migrations-flyway
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/jabrena/plinth.git /tmp/plinth
mkdir -p .claude/skills
cp -r /tmp/plinth/skills/313-frameworks-spring-db-migrations-flyway .claude/skills/313-frameworks-spring-db-migrations-flyway
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable 313 Frameworks Spring Db Migrations Flyway in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads 313 Frameworks Spring Db Migrations Flyway on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so 313 Frameworks Spring Db Migrations Flyway is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Spring — Database migrations (Flyway)

Apply Flyway migration guidelines for Spring Boot.

What is covered in this Skill?

  • flyway-core and database-specific Flyway modules (e.g. PostgreSQL) with Spring Boot BOM
  • Versioned SQL under src/main/resources/db/migration (V{version}__{description}.sql)
  • spring.flyway.* properties: locations, baseline-on-migrate, validate-on-migrate
  • Optional Java migrations (BaseJavaMigration) for data backfills
  • Forward-only discipline: do not rewrite applied migrations in shared environments
  • Parallel Change as the safe expand, migrate, contract workflow for breaking or data-sensitive schema changes
  • Coordination with @311-frameworks-spring-jdbc and @312-frameworks-spring-data-jdbc

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 Spring Boot project
  • Configure spring.flyway or db/migration layout
  • Add versioned Flyway SQL migrations for Spring Boot
  • Review Spring Boot database migration ordering
  • Fix repeatable Flyway migrations in a Spring project

Workflow

  1. Read references and assess project context

Read references/313-frameworks-spring-db-migrations-flyway.md, references/313-frameworks-spring-db-migrations-flyway-antipatterns.md, and references/313-frameworks-spring-db-migrations-flyway-parallel-change.md, then inspect the current project setup before proposing changes.

  1. Gather scope and decide target improvements

Identify requested outcomes, constraints, and the minimum safe set of changes to apply.

  1. 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.

  1. 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:

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the 313 Frameworks Spring Db Migrations Flyway AI skill do?

Use when you need to add or review Flyway database migrations in a Spring Boot application — Maven dependencies, db/migration scripts, spring.flyway.* configuration, baseline and validation, and alignment with JDBC or Spring Data JDBC. This should trigger for requests such as Add or review Flyway migrations in a Spring Boot project; Configure spring.flyway or db/migration layout; Add versioned Flyway SQL migrations for Spring Boot; Review Spring Boot database migration ordering; Fix repeatable Flyway migrations in a Spring project. Part of Plinth Toolkit

Why use 313 Frameworks Spring Db Migrations Flyway on TypingMind?

Because you install it once and use it with any model. 313 Frameworks Spring Db Migrations Flyway is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install 313 Frameworks Spring Db Migrations Flyway in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/jabrena/plinth/tree/main/skills/313-frameworks-spring-db-migrations-flyway. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use 313 Frameworks Spring Db Migrations Flyway?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with 313 Frameworks Spring Db Migrations Flyway?

As many as you like. As long as a model supports skills, you can use 313 Frameworks Spring Db Migrations Flyway with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the 313 Frameworks Spring Db Migrations Flyway AI skill free?

Yes. It is published on GitHub by jabrena under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇