Menu
Change risk analysis — blast radius, affected systems, and what to test. Depth scales with risk level; low-risk targets stop early.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
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.
Build a mental model of a system, subsystem, or the whole repo. Graph-first, no code reads unless necessary.
| 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. |
| metadata | {"openclaw":{"requires":{"bins":["ix"]}}} |
Run command -v ix to verify ix is on PATH. Never use tilde paths (~/...) or absolute paths — always invoke ix directly via PATH. If not found, use Grep to find all usages and estimate impact manually.
Answer: what breaks if this changes, and is it safe to proceed? Stop as early as the risk level allows.
timeout 60s ix impact $ARGUMENTS --format llm
Immediately classify:
| 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 |
Run in parallel:
timeout 60s ix callers $ARGUMENTS --limit 20 --format llm
timeout 60s ix depends $ARGUMENTS --depth 2 --format llm
Extract: direct callers by name and subsystem, transitive count.
Stop here if risk is medium: report callers, suggest verification, done.
timeout 60s ix imported-by $ARGUMENTS --format llm
Cross-reference callers + dependents + importers to identify:
## 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 atRiskBehavior 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. Risk analysis is purely graph-based.