impact-analysis

Identify downstream impacts across hooks, scripts, and installed components after kit infrastructure changes.

Updated Feb 9, 2026
One-click install
npx skills add https://github.com/Xza85hrf/claude-code-agent-kit --skill impact-analysis-xza85hrf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: impact-analysis
Source: https://github.com/Xza85hrf/claude-code-agent-kit/tree/main/.claude/skills/quality/impact-analysis
Command: npx skills add https://github.com/Xza85hrf/claude-code-agent-kit --skill impact-analysis-xza85hrf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic blast radius review after infrastructure changes. Validate deployment vectors, check cross-references, and catch broken paths or orphaned references before landing.

Core Features & Use Cases

  • Identify downstream impacts across shared libraries, deploy scripts, and configuration files.
  • Validate cross-references and plugin integrations to prevent regressions in complex kit setups.
  • Use after modifying kit internals (hooks, scripts, libs, profiles, and plugin.json) to catch orphaned references and broken install paths.
  • Use Case: before merging changes, run a blast-radius analysis and review the generated report to decide safe next steps.

Quick Start

Run the blast-radius analysis after infra changes to ensure no unintended impacts.

Frequently Asked Questions about impact-analysis

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

FAQPage Schema
How do I check the blast radius of infrastructure changes before merging?

Downstream impacts from shared library and deploy script modifications are identified by validating cross-references and plugin integrations. This process catches orphaned references and broken install paths across kit hooks, profiles, and configurations.

What is the best way to catch broken paths and orphaned references after modifying kit internals?

The best way to catch orphaned references after modifying kit internals is to run a blast-radius analysis. It validates cross-references across hooks, scripts, libs, and plugin.json files to prevent regressions in complex setups before landing changes.

Do I need to run cross-reference checks for every shared library and profile update?

Yes, cross-reference checks are required for shared library and profile updates to ensure safe rollback readiness. Validating plugin configurations and deploy scripts prevents broken install paths and unintended regressions across installed components.

Does blast-radius analysis validate deployment vectors and rollback readiness for plugin configurations?

Blast-radius analysis validates deployment vectors and confirms rollback readiness for plugin configurations. It systematically reviews generated outputs and deploy scripts to ensure no broken paths or orphaned references remain after infrastructure changes.

When should I not use an impact analysis for infrastructure changes?

Impact analysis for infrastructure changes should not be skipped before merging complex kit setups. Without validating cross-references and deployment vectors, orphaned references and broken install paths may cause severe regressions across shared libraries and profiles.