impact

Generate risk-rated impact reports for modified modules with consumer enumeration.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/ImLp/claude-caide --skill impact-imlp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: impact
Source: https://github.com/ImLp/claude-caide/tree/main/.claude/skills/impact
Command: npx skills add https://github.com/ImLp/claude-caide --skill impact-imlp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Produce a risk-rated impact report for a given module before modifications, renames, or removals. Identifies direct and transitive consumers, assesses blast radius, and determines whether an Architectural Decision Record is required. Read-only — makes no changes.

Core Features & Use Cases

  • Resolve a target module or symbol and locate its wiki pages to build an impact map.
  • Enumerate direct and transitive consumers, capturing relationship types and blast radii.
  • Determine whether an ADR is required and present a structured impact report for decision making.

Quick Start

Run the impact workflow against a target module, for example /impact EventBus, to generate the report.

Frequently Asked Questions about impact

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

FAQPage Schema
How do I generate an impact analysis report for a module before modifying it?

Generate an impact analysis report by resolving a target module and enumerating its direct and transitive consumers. The report assesses the blast radius and determines whether an ADR is required before modifications.

When do I need an ADR for a code dependency modification?

You need an ADR for a code dependency modification when the impact report indicates a significant blast radius across transitive consumers. The report evaluates the risk of changes to determine if an ADR is required.

How do I assess the blast radius of removing a symbol across a wiki?

Assess the blast radius of a symbol removal by locating its wiki pages to build an impact map. The system enumerates direct and transitive consumers to quantify the fallout and capture relationship types.

Can I use this to analyze transitive consumers without making actual code changes?

Yes, you can analyze transitive consumers without making code changes because the process is strictly read-only. It resolves symbol relationships to generate an organized, auditable risk report without modifying files.

What is the best way to identify transitive consumers of a file before a rename?

The best way to identify transitive consumers before a rename is to run an impact workflow against the target. It resolves the file or module across the wiki to capture relationship types and quantify potential fallout.

Does the impact report work for both modules and individual symbols?

Yes, the impact report works for modules, files, and individual symbols. It requires a wiki-view of dependencies to locate target pages and enumerate consumers for the risk assessment.