database-change-management

name	database-change-management
description	Plan and implement safe schema, migration, relationship, index, query, and backfill changes with rollback awareness. Use when data shape or persistence contracts change.

Database Change Management

Use this skill when work touches schema, migrations, indexes, query behavior, or data-shape contracts.

Workflow

1. Audit current schema usage, models, and dependent code.
2. Implement additive and reversible changes by default. Only generate destructive changes if explicitly mandated by the user.
3. Document migration order, rollback expectations, and any backfill requirements.
4. Update related models, queries, and tests.
5. If migration patterns, rollout decisions, or incident context need extra context and the user enabled a relevant MCP, load the matching mcp-* skill first.
6. Discover migration and verification commands from repository config and docs before execution. Run the narrowest non-destructive validation first. If no command exists, record a manual dry-run query or code check. If validation fails, fix in-scope migration issues; otherwise report the blocker with the relevant error summary.

Rules

• Avoid destructive changes without an explicit rollback or data-preservation plan.
• Prefer nullable or defaulted additions for existing tables.
• Do not apply migrations against production or shared live data unless the user explicitly requested that action.
• Record deployment notes when migration sequencing matters.

Relevant MCP Skills

• mcp-context7 for migration, ORM, and database-tool documentation
• mcp-github for migration-related PR, issue, or workflow context
• mcp-sentry for production failures tied to schema or query regressions
• mcp-open-bridge for sequencing review, rollback trade-offs, and tricky query or schema analysis

Output

Report:

• Schema or data change
• Files updated
• Rollback or deployment notes
• Verification run