validate-migration

validate-migration is a skill for Claude Code from ivanhoinacki/team-exp-claude-config. It costs 64 tokens per session (3,307 once invoked), scanned A, original, MIT.

A checklist for reviewing database migrations, which are changes that update a database’s tables, columns, indexes, or constraints.

In plain words
What is it for?
Use it to review migrations, index creation, schema changes, column changes, and zero-downtime deployment plans.
Why use it?
It helps identify missing rollback plans, compatibility problems, table locks, performance risks, and unsafe changes before they reach production.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter; mentions subagents.

Good fit Use it to review migrations, index creation, schema changes, column changes, and zero-downtime deployment plans.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ivanhoinacki/team-exp-claude-config/validate-migration
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 ivanhoinacki/team-exp-claude-config --skill validate-migration
Clone the repo
git clone --depth 1 https://github.com/ivanhoinacki/team-exp-claude-config

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 validate-migration

README.md
[![agentmods](https://agentmods.dev/badge/skills/ivanhoinacki/team-exp-claude-config/validate-migration/github.svg)](https://agentmods.dev/skills/ivanhoinacki/team-exp-claude-config/validate-migration)
Your own site
<a href="https://agentmods.dev/skills/ivanhoinacki/team-exp-claude-config/validate-migration"><img src="https://agentmods.dev/badge/skills/ivanhoinacki/team-exp-claude-config/validate-migration/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 validate-migration

Your own site · 80×15
<a href="https://agentmods.dev/skills/ivanhoinacki/team-exp-claude-config/validate-migration"><img src="https://agentmods.dev/badge/skills/ivanhoinacki/team-exp-claude-config/validate-migration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 64 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,307 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.00064 $0.03307
Opus 5 $0.00032 $0.01654
Sonnet 5 $0.00013 $0.00661
Haiku 4.5 $0.00006 $0.00331

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

Security

Grade A, and why

validate-migration 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.

skills/validate-migration/SKILL.md · 367 lines

How it starts

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

Phase 0: Vault RAG (MANDATORY, BEFORE any Read/Grep)

You MUST call query_vault(query, service_filter) BEFORE reading codebase files or external sources. This is enforced by hook. No exceptions.


Validate Migration

Working Directories

  1. Obsidian workspace: __VAULT_ROOT__
  2. Codebase: __CODEBASE_ROOT__

Common Agent Mistakes

  1. No rollback plan: Approving a migration without verifying down() exists and is correct. Every migration MUST have a working rollback or explicit acknowledgment of irreversibility.
  2. Missing CONCURRENTLY: Not flagging CREATE INDEX without CONCURRENTLY on any table. This locks the table for writes during index creation.
  3. Ignoring dual-database (svc-experiences): Validating the migration SQL but not reminding about the dual-database requirement. Both dev and spec databases need migration.
  4. Underestimating table size: Not checking the large table risk list before approving an ALTER TABLE. Always cross-reference Phase 2 table.
  5. Single-step risky operations: Not suggesting zero-downtime recipes for column renames, type changes, or constraint additions on large tables. Always recommend the multi-step approach.
  6. Transaction + CONCURRENTLY conflict: Not catching CREATE INDEX CONCURRENTLY inside a transaction. TypeORM wraps migrations in transactions by default.

Phase 0: Discover and Classify

Find migration files

  1. If $ARGUMENTS provided, use that path directly
  2. Otherwise, find migration files in the current branch diff:
GIT_EDITOR=true git diff --name-only main...HEAD | grep -iE "(migrat|\.sql)"

Detect ORM framework

Service ORM Migration format Location
svc-experiences TypeORM TypeScript classes with up()/down() src/migration/
svc-order Sequelize JS files with up()/down() db/migrations/
svc-ee-offer Sequelize JS files db/migrations/
svc-search Sequelize JS files db/migrations/
svc-auth Prisma .prisma schema + SQL prisma/migrations/

Read the full file on GitHub · 367 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 · 367 lines · 64 tokens per session scan A a4817fcc783c

Subscribe to this mod's changes

validate-migration is a skill published in the GitHub repository ivanhoinacki/team-exp-claude-config (2 stars, last pushed 1mo ago), licensed MIT. It adds 64 tokens to every session and 3,307 once invoked, about $0.0003 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-31.

Related

Other skills, from other repositories