Menu
Use BEFORE editing, renaming, or deleting any function, class, or method, to avoid breaking dependents.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Use when reviewing a PR, a diff, or recent changes, to get a full risk assessment in one call.
Use at the START of any code task (fix, extend, refactor, understand) before reading source files, to orient with ctxo and avoid going in the wrong direction.
| name | ctxo-safe-edit |
| description | Use BEFORE editing, renaming, or deleting any function, class, or method, to avoid breaking dependents. |
Before changing a symbol, in order - do NOT skip:
get_blast_radius(symbolId) - see what breaks. If confirmed/likely dependents exist, plan to update them too.get_why_context(symbolId) - check for revert history or anti-patterns. If found, STOP and tell the user instead of repeating a reverted approach.A deterministic guard may block the first edit of a high-impact symbol until you have run get_blast_radius. That is expected - run it, then re-issue the edit.