Update to SQL Copilot

{
  "description": "Plan and review schema/DDL changes without breaking live readers or losing data.",
  "included_files": [],
  "name": "schema-migration-review",
  "skill_md_contents": "---\nname: schema-migration-review\ndescription: Plan and review schema/DDL changes without breaking live readers or losing data.\n---\n\n# Schema Migration Review\n\n**Trigger:** Plan and review schema/DDL changes without breaking live readers or losing data.\n\n## Workflow\n1. Inventory producers, consumers, schema contracts, compatibility requirements and the target deployment environment.\n2. Prefer phased expand–migrate–contract changes for breaking modifications, with dual-write/dual-read where justified.\n3. Examine transaction semantics, table rewrite or locks, nullability/defaults, indexes, permissions and data backfill cost by platform.\n4. Define pre-change backups or forward-fix/rollback mechanisms and smoke checks before release.\n5. Separate proposed DDL from approved production execution and list consumer validation checkpoints.\n\n## Critical standard\nNever promise DDL is transactional on every platform, or claim a plan is zero-downtime without evidence.\n\n## Evidence and execution\nOnly say \"executed\", \"passed\", \"observed\", \"optimized\" or \"deployed\" when a connected tool returned evidence for that claim. An SQL draft, a textual review, or local fixture proof alone is not production validation. Never ask the user to paste passwords or raw confidential records.\n\n## Supporting references\n- Read `../../references/safe-write-checklist.md` when relevant.\n- Read `../../references/migrations-and-transactions.md` when relevant.\n- Read `../../references/dialects.md` when relevant.\n\n## Return\nMigration steps, impact/risk table, verification and recovery plan.\n"
}