DATABASES / JetBrains
Schema Migration Planner
Plans database schema changes as phased expand, dual-write, backfill, switch-read, contract sequences with explicit lock, replication and rollback-safety analysis, instead of a single DDL statement.
“Plan safe database schema evolution and zero-downtime change rollout for Kotlin plus Spring systems using Flyway, Liquibase, or equivalent migration tooling.”
01 / THE REASONING
Why this made the selection.
- Encodes expand/contract migration as a planning contract: classify the change as additive, destructive, semantic or data-moving, decide whether old and new application versions must coexist, then phase the rollout and treat cleanup as a separate step behind an explicit proof threshold.
- Names operational traps: non-null column adds that rewrite or lock large tables, backfills that saturate replicas and CDC consumers while primary write latency looks fine, renames that are copy-switch-drop plans in disguise.
- The output contract forces operational-risk and verification sections, so a run produces a reviewable migration plan rather than correct-but-dangerous SQL.
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- schema-migration-planner/SKILL.md (JetBrains mirror, complete, 107 lines)
- schema-migration-planner/agents/openai.yaml (identical to upstream)
- upstream yalishevant/kotlin-backend-agent-skills schema-migration-planner SKILL.md
- upstream yalishevant/kotlin-backend-agent-skills LICENSE
- JetBrains/skills README mirror policy
- https://github.com/Kotlin/kotlin-backend-agent-skills (answers HTTP 301 to yalishevant/kotlin-backend-agent-skills)
- mirror SKILL.md diffed against the upstream SKILL.md at fd0ed521d22efd28221d532c9abab97af0b9bf0e
Our findings
- The planning workflow classifies the change first and makes old/new code coexistence an explicit decision before any rollout phase is planned.
- Guardrails forbid direct destructive DDL on live systems without a phased plan and refuse to assume rollback is safe once data has been transformed.
- A diff against the upstream SKILL.md at fd0ed521d22efd28221d532c9abab97af0b9bf0e shows the mirror adds four frontmatter lines (metadata, short-description, author: Kotlin, source) and nothing else; the upstream file has no author field. agents/openai.yaml is identical in both.
- Upstream health: https://github.com/Kotlin/kotlin-backend-agent-skills, which the mirror’s metadata.source and README name, now answers HTTP 301 to yalishevant/kotlin-backend-agent-skills, a personal account (https://api.github.com/repos/Kotlin/kotlin-backend-agent-skills returns full_name yalishevant/kotlin-backend-agent-skills, owner type User). fd0ed521d22efd28221d532c9abab97af0b9bf0e is still that repository’s head, and its LICENSE (MIT, copyright 2026 Anton Yalyshev) is unchanged (checked 2026-10-13).
Not established by this review
- No migration was planned against a real schema and no SQL was executed.
- Lock, backfill and replication behaviour claims were not measured on any database.
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Add a skill to your workflow.
DOCUMENTED COMMAND
npx skills add JetBrains/skills/schema-migration-planner --skill schema-migration-planner Run in your terminal to choose your AI tools, project or global scope, and installation method. This short command follows the current upstream version; the review covers the revision shown above.
Optional: install the reviewed revision
Keeps the original source and installer version where recorded, while leaving your AI tools and installation scope for you to choose.
npx skills add https://github.com/JetBrains/skills/tree/e0f258b5cfed145015cb3e48da9a97947f7c4ed7/schema-migration-planner --skill schema-migration-planner - Install the complete skill directory; the agents profile travels with the SKILL.md.
- Bring the current schema, target shape and deployment model; expect a phased plan with an explicit compatibility story, not a single migration script.
Before you start
- Node.js/npm for the installer
- An agent that supports the Agent Skills format
- Schema access, table sizes and the migration tool actually in use
04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
https://github.com/JetBrains/skills/blob/e0f258b5cfed145015cb3e48da9a97947f7c4ed7/schema-migration-planner/SKILL.md
Supports: summary, upstreamDescription, whySelected, bestFor, limitations, review, access
https://github.com/yalishevant/kotlin-backend-agent-skills/blob/fd0ed521d22efd28221d532c9abab97af0b9bf0e/.agents/skills/schema-migration-planner/SKILL.md
Supports: review, limitations
- Upstream licence (MIT) ↗Checked
https://github.com/yalishevant/kotlin-backend-agent-skills/blob/fd0ed521d22efd28221d532c9abab97af0b9bf0e/LICENSE
Supports: license
https://github.com/Kotlin/kotlin-backend-agent-skills
Supports: review, limitations
https://github.com/JetBrains/skills/blob/e0f258b5cfed145015cb3e48da9a97947f7c4ed7/README.md
Supports: review, install, limitations
https://github.com/vercel-labs/skills/blob/7407f3893ad4dceab546ac002c3ef806e4000c73/README.md
Supports: install