One-click install
npx skills add https://github.com/ix-infrastructure/ix-claude-plugin --skill ix-impact
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ix-impact
Source: https://github.com/ix-infrastructure/ix-claude-plugin/tree/main/skills/ix-impact
Command: npx skills add https://github.com/ix-infrastructure/ix-claude-plugin --skill ix-impact

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ix-impact helps you understand what will likely break when you change a symbol or file by estimating blast radius, affected subsystems, and what to test before you edit.

Core Features & Use Cases

  • Graph-based risk classification: Computes a risk level using Ix graph queries and explains how influence is distributed, then stops early for low-risk targets.
  • Caller/dependent impact mapping: For medium to critical risk, enumerates direct callers and assesses transitive dependents to guide verification scope.
  • High/critical spread analysis: For higher risk, traces import chains and subsystem spread to reveal architectural boundary crossings.
  • Output tailored to action: Produces a verdict (safe, review, or plan-first) plus recommended next steps, and optionally flags known bugs in the blast radius when Pro is available.

Quick Start

Ask for impact analysis by writing: ix-impact api/client.ts --save impact-report.md

Frequently Asked Questions about ix-impact

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I assess change risk and blast radius before refactoring a file?

Change risk analysis evaluates blast radius across callers, dependents, and subsystem spread using dependency graph queries. It classifies risk levels to guide verification scope and planning for safer edits and refactors.

What is dependency graph based test planning for safe refactors?

Dependency graph based test planning identifies affected callers and transitive dependents to define verification scope. It traces import chains and architectural boundary crossings to ensure comprehensive test coverage for refactors.

How do I map callers and dependents to plan safer code edits?

Mapping callers and dependents involves enumerating direct callers and assessing transitive dependents via graph queries. For high risk targets, it traces import chains and subsystem spread to reveal architectural boundary crossings.

Can I save a markdown report of architecture impact analysis?

Yes, you can save a markdown report of architecture impact analysis by appending the save flag with a filename. This exports the risk verdict, caller mapping, and recommended next steps to a markdown file.

Does change risk analysis stop early for low-risk code modifications?

Yes, change risk analysis stops early for low-risk targets. It scales depth based on risk level, skipping deep caller enumeration and subsystem spread tracing when the estimated blast radius is minimal.

What are the limitations of using blast radius estimation for feature work?

Blast radius estimation relies on graph query availability and does not execute code, so it cannot detect runtime behavioral risks. Optional known bug cross-referencing requires Pro access to flag issues within the affected scope.