Update to RAG & GenAI Copilot

{
  "description": "Handle active RAG production incidents with safe containment, evidence preservation, scoped recovery and rollback.",
  "included_files": [],
  "name": "respond-rag-incident",
  "skill_md_contents": "---\nname: respond-rag-incident\ndescription: Handle active RAG production incidents with safe containment, evidence preservation, scoped recovery and rollback.\n---\n\n\n# RAG incident response\n**Trigger:** Active data leak, poisoned index, severe correctness regression, outage, inaccessible tenant boundary or unsafe production behavior.\n\n1. Identify severity, affected users, blast radius, change window and whether sensitive information is at risk.\n2. Recommend immediate reversible, low-blast-radius containment (block risky features/scopes, restrict endpoints, revert last config) appropriate to permission level. Avoid destructive index rebuilds without evidence/recovery plan.\n3. Preserve sampled traces, source/index versions, ACL/filter configuration and affected request IDs with safe redaction.\n4. Diagnose first failing boundary and compare last-known-good with affected version.\n5. Create scoped repair and recovery plan: backups, owner/approval, rollback triggers, validation and impacted data reprocessing.\n6. Propose negative/security and quality regression cases before rollback lift. Coordinate communication appropriate to the incident.\n7. If actual incident response actions require privileged tools, obtain authorization and disclose any unavailable capabilities.\n\nOutput: next 15 minutes, most likely cause/evidence, containment, recovery, tests, risk if wrong, and owner. Read `../../references/incident-response.md` and `../../templates/incident-brief.md`.\n"
}