flyway-or-liquibase-detection

flyway-or-liquibase-detection is a skill for Claude Code from loiane/specs-driven-development-spring-angular. It costs 35 tokens per session (836 once invoked), scanned A, original, MIT.

A project check that identifies whether a Java application uses Flyway or Liquibase, two tools for tracking database schema changes, and applies the matching file and version rules.

In plain words
What is it for?
Use it when designing or writing a database schema change, such as adding a table, index, view, or function.
Why use it?
It prevents mixing the two migration tools or placing changes in the wrong format. It also keeps database changes forward-only and records rollback planning for destructive changes.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it when designing or writing a database schema change, such as adding a table, index, view, or function.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/loiane/specs-driven-development-spring-angular/flyway-or-liquibase-detection
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add loiane/specs-driven-development-spring-angular --skill flyway-or-liquibase-detection
Clone the repo
git clone --depth 1 https://github.com/loiane/specs-driven-development-spring-angular

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for flyway-or-liquibase-detection

README.md
[![agentmods](https://agentmods.dev/badge/skills/loiane/specs-driven-development-spring-angular/flyway-or-liquibase-detection/github.svg)](https://agentmods.dev/skills/loiane/specs-driven-development-spring-angular/flyway-or-liquibase-detection)
Your own site
<a href="https://agentmods.dev/skills/loiane/specs-driven-development-spring-angular/flyway-or-liquibase-detection"><img src="https://agentmods.dev/badge/skills/loiane/specs-driven-development-spring-angular/flyway-or-liquibase-detection/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for flyway-or-liquibase-detection

Your own site · 80×15
<a href="https://agentmods.dev/skills/loiane/specs-driven-development-spring-angular/flyway-or-liquibase-detection"><img src="https://agentmods.dev/badge/skills/loiane/specs-driven-development-spring-angular/flyway-or-liquibase-detection.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 836 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00035 $0.00836
Opus 5 $0.00017 $0.00418
Sonnet 5 $0.00007 $0.00167
Haiku 4.5 $0.00003 $0.00084

Measured 9d ago against content hash a3cd5aae9bf8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

flyway-or-liquibase-detection scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/flyway-or-liquibase-detection/SKILL.md · 79 lines

How it starts

The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Flyway or Liquibase detection

Detection

.github/scripts/detect-stack.sh reports one of:

  • flywayflyway-core in pom.xml AND src/main/resources/db/migration/ exists.
  • liquibaseliquibase-core in pom.xml AND src/main/resources/db/changelog/ exists.
  • none — neither.
  • bothfatal. Refuse to proceed; ask the user to remove one.

Record the result in 03-design.md under ### Inputs from detect-stack.sh.

Flyway conventions

  • File path: src/main/resources/db/migration/V{version}__{description}.sql
  • Versioning: V1__init.sql, V2__add_gift_card_table.sql, V3__add_index_gift_card_code.sql
  • One migration per logical change. Never edit a checked-in migration; add a new one.
  • Repeatable migrations (views, functions): R__view_active_orders.sql.
  • Forward-only by default. If a migration is destructive, the design must include a ## Rollback section in 03-design.md.
-- V12__add_gift_card_table.sql
CREATE TABLE gift_card (
    id          UUID PRIMARY KEY,
    code        VARCHAR(64) NOT NULL UNIQUE,
    balance     NUMERIC(12,2) NOT NULL CHECK (balance >= 0),
    created_at  TIMESTAMPTZ NOT NULL DEFAULT now()
);
CREATE INDEX ix_gift_card_code ON gift_card(code);

Liquibase conventions

  • Master changelog: src/main/resources/db/changelog/db.changelog-master.yaml
  • Per-feature changeset file: db/changelog/changes/2026-04-18-gift-card.yaml
  • Include via <include file="changes/2026-04-18-gift-card.yaml"/>.
  • Each changeset has id, author, and is immutable once merged.
databaseChangeLog:
  - changeSet:
      id: gift-card-1
      author: spring-implementer
      changes:
        - createTable:
            tableName: gift_card
            columns:
              - column: { name: id, type: UUID, constraints: { primaryKey: true } }
              - column: { name: code, type: VARCHAR(64), constraints: { nullable: false, unique: true } }
              - column: { name: balance, type: NUMERIC(12,2), constraints: { nullable: false } }
              - column: { name: created_at, type: TIMESTAMPTZ, defaultValueComputed: now() }

Read the full file on GitHub · 79 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 79 lines · 0 tokens per session scan A a3cd5aae9bf8

Subscribe to this mod's changes

flyway-or-liquibase-detection is a skill published in the GitHub repository loiane/specs-driven-development-spring-angular (59 stars, last pushed 2mo ago), licensed MIT. It adds 35 tokens to every session and 836 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

spec-kitty-mission-review

Review a fully merged Spec Kitty mission post-merge (all WPs done/approved) to verify spec→code fidelity, FR coverage, drift, risks, and security. Triggers: "review the merged mission", "post-merge mission review", "verify the completed mission", "audit the mission implementation", "mission-level acceptance review"…

Priivacy-ai/spec-kitty · 155 tokens

spec-kitty-mission-system

Understand how Spec Kitty missions work: the 4 built-in mission types, how they define workflows via step contracts and action indices, how missions and work packages relate, how templates are resolved through the 6-tier chain, and how doctrine artifacts (procedures, tactics, directives) compose mission behavior.…

Priivacy-ai/spec-kitty · 160 tokens

spec-kitty-runtime-next

Drive the canonical spec-kitty next --mission control loop for mission advancement. Load agent profiles at init, apply action-scoped doctrine context at each step boundary, and pull specific tactics/directives on demand. Triggers: "run the next step", "what should runtime do next", "advance the mission", "what is the…

Priivacy-ai/spec-kitty · 110 tokens

spec-kitty-git-workflow

Understand how Spec Kitty manages git: what git operations Python handles automatically, what agents must do manually, worktree lifecycle, auto-commit behavior, merge execution, and the safe-commit pattern. Triggers: "how does spec-kitty use git", "worktree management", "auto-commit", "who commits what", "git…

Priivacy-ai/spec-kitty · 125 tokens

spec-kitty-spdd-reasons

Drive REASONS Canvas authoring and review for Spec Kitty missions that opted in to Structured-Prompt-Driven Development (SPDD) via charter selection. Triggers: "use SPDD", "use REASONS", "generate a REASONS canvas", "apply structured prompt driven development", "make this mission SPDD". Does NOT handle: enforcing SPDD…

Priivacy-ai/spec-kitty · 118 tokens

spec-kitty-runtime-review

Review runtime-owned outputs using the Spec Kitty review workflow surface, then direct approval or rejection with structured feedback. Triggers: "review this work package", "check runtime output", "approve this step", "review WP", "is this WP ready to approve", "check this implementation". Does NOT handle: setup-only…

Priivacy-ai/spec-kitty · 85 tokens