Menu
Change risk analysis — blast radius, affected systems, and what to test. Depth scales with risk level; low-risk targets stop early.
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.
Based on SOC occupation classification
Route to the right Ix skill or command for your task
Analyze system design — structure, coupling, code smells, and high-risk hotspots. Purely graph-based, no code reads.
Root cause analysis — trace execution path to a failure, narrow candidates, read minimal source only at suspected failure points.
Generate narrative-first, importance-weighted documentation for a repo, system, or subsystem with a selective reference layer. Use --full for deeper module/class/method coverage.
Deep dive into a symbol, feature, or bug. Graph-first, minimal code reads, early stopping when sufficient evidence found.
Generate a risk-ordered implementation plan for a set of targets. Assesses blast radius per target, finds data flows between them, and produces a safe change sequence.
| name | ix-impact |
| description | Change risk analysis — blast radius, affected systems, and what to test. Depth scales with risk level; low-risk targets stop early. |
Answer: what breaks if this changes, and is it safe to proceed? Stop as early as the risk level allows.
If the Ix runtime is unavailable, ix_status will report this; estimate impact from available context.
For most cases:
ix_query({ mode: "impact", targets: [$ARGUMENTS] })
Use the returned preview_markdown as the primary answer. Supplement below if risk classification needs detail.
Call: ix_impact({ target: $ARGUMENTS })
Immediately classify on risk_level and dependents:
| Risk level | Action |
|---|---|
low + < 3 dependents | STOP — safe to proceed. Report and suggest verification targets. |
medium OR 3-10 dependents | Go to Phase 2 |
high or critical OR > 10 dependents | Go to Phase 2 + 3 |
Call in parallel:
ix_callers({ symbol: $ARGUMENTS })ix_depends({ symbol: $ARGUMENTS, depth: 2 })Stop here if risk is medium.
Call: ix_imported_by({ symbol: $ARGUMENTS })
Cross-reference callers + dependents + importers to identify subsystems in the blast radius.
## Impact: [target]
**Risk level:** <critical | high | medium | low>
**Verdict:** <SAFE TO PROCEED | REVIEW CALLERS FIRST | NEEDS CHANGE PLAN>
**Blast radius:**
- Direct dependents: N
- Transitive (depth 2): M
- Subsystems affected: [list — only if phase 3 ran]
**Key callers:** [top 5, with subsystem label]
**At-risk behaviors:** [from ix_impact at_risk_behavior field]
**Recommended action:**
- low: proceed, verify [specific callers]
- medium: test [caller list] after change
- high/critical: run `ix-plan $ARGUMENTS` before editing
Never read source code in this skill.