Menu
Use BEFORE editing, renaming, or deleting any function, class, or method, to avoid breaking dependents.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
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.
Based on SOC occupation classification
| 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.