db-migration-review
review database migrations for safety, compatibility windows, backfills, reversibility, and rollout risk. use when migration files, schema diffs, orm model changes, indexes, constraints, or data backfills change.
- License 许可
- GPL-3.0
- 最近更新
- 2026-05-19
- Stars
- ★ 6
- Forks
- 1
01 前言 Front Matter
- name
- db-migration-review
- description
- review database migrations for safety, compatibility windows, backfills, reversibility, and rollout risk. use when migration files, schema diffs, orm model changes, indexes, constraints, or data backfills change.
02 资源文件 7
- 参考文档references/engine-specific-hotspots.md937 B
- 参考文档references/examples.md482 B
- 参考文档references/expand-contract.md876 B
- 参考文档references/review-template.md446 B
- 参考文档references/risk-taxonomy.md1.1 KB
- 参考文档references/rollout-and-backfill.md804 B
- 参考文档references/tooling-signals.md1001 B
03 SKILL.md 正文
DB Migration Review
Trigger Signals
- the task adds or edits migrations, DDL, backfills, seed data, or schema-affecting ORM changes
- the change touches EF Core, Flyway, Liquibase, Prisma, Atlas, handcrafted SQL, or online migration tooling
- rollout safety matters because the database is large, hot, replicated, or shared by multiple services
Inspect First
- migration files, generated SQL, and schema model diffs
- the application code that reads or writes the changed tables or columns
- deployment order, backfill jobs, feature flags, and rollback expectations
- table size, hot paths, index usage, and engine-specific lock sensitivity when evidence exists
Workflow
- classify the change as additive, destructive, rewrite-heavy, data-moving, or operationally sensitive
- determine the compatibility window between old code, new code, and intermediate schema states
- inspect lock, rewrite, replication, and backfill risk with the engine and tool in mind
- verify reversibility, forward-fix options, and post-deploy validation steps
- emit a risk-ranked review with concrete rollout guidance, not generic warnings
Output Contract
- migration summary grouped by schema change, data change, and rollout shape
- risk level with the exact reasons it is safe, risky, or blocked
- expand-and-contract verdict, rollback or forward-fix plan, and validation queries or checks
- follow-up tasks for app changes, monitoring, throttling, or staged deployment
Failure Modes
- engine, table size, or traffic profile is unknown and materially changes risk
- the migration file exists without the surrounding application rollout plan
- generated SQL is unavailable for toolchains that hide the real DDL
Escalation
- escalate when a migration can drop data, rewrite a large table, block hot paths, or break mixed-version application deployments
- escalate when backfills are non-idempotent, unthrottled, or lack checkpointing
- escalate when rollback is impossible and no forward-fix path or validation telemetry exists
References
skills/db-migration-review/references/risk-taxonomy.mdskills/db-migration-review/references/expand-contract.mdskills/db-migration-review/references/engine-specific-hotspots.mdskills/db-migration-review/references/tooling-signals.mdskills/db-migration-review/references/rollout-and-backfill.mdskills/db-migration-review/references/review-template.mdskills/db-migration-review/references/examples.md
04 同仓库更多 Skills
typescript-engineering
typescript and javascript engineering guidance seeded from the harness forge knowledge base. use when the repo or task is dominated by .ts, .tsx, package.json, tsconfig, node.js services, react, next.js, frontend tooling, or multi-package workspaces where type boundaries matter.
token-budget-optimizer
compact context, reuse existing runtime artifacts, and choose the smallest authoritative surface before expanding prompt history. use when the task is growing large, when earlier repo intelligence already exists, or when repeated rescans would waste tokens without adding new evidence.
test-strategy-and-coverage
Define right-sized test layers and coverage priorities for a change.
speckit-taskstoissues
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
speckit-tasks
Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
speckit-specify
Create or update the feature specification from a natural language feature description.