Update to SQL Copilot

{
  "description": "Review and generate carefully scoped UPDATE, DELETE, INSERT and MERGE operations.",
  "included_files": [],
  "name": "safe-sql-writes",
  "skill_md_contents": "---\nname: safe-sql-writes\ndescription: Review and generate carefully scoped UPDATE, DELETE, INSERT and MERGE operations.\n---\n\n# Safe Sql Writes\n\n**Trigger:** Review and generate carefully scoped UPDATE, DELETE, INSERT and MERGE operations.\n\n## Workflow\n1. Classify target, environment, authorization, row-scope and reversibility before any write guidance.\n2. Produce a READ-ONLY preview of the exact target row set and affected row counts; include duplicate-match checks for UPDATE FROM/MERGE.\n3. Explicitly separate read-only preview queries from potentially mutating SQL with an unmistakable warning heading.\n4. Recommend transaction/backup/snapshot/restore strategies only when they actually apply to the dialect and operation.\n5. For remote execution, require appropriate user authorization, least privileges and confirmations; do not execute directly through unspecified tools.\n\n## Critical standard\nNever present broad unqualified destructive SQL as harmless. Match preview predicates to the proposed write.\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/original/sql_write_change_playbook.md` when relevant.\n- Read `../../references/dialects.md` when relevant.\n\n## Return\nScope statement, preview SQL, validation gates and separate optional write SQL.\n"
}