Change Impact Analysis

Predict impacts of architectural changes on dependent systems. Trace dependencies, assess risk, plan rollout. Use when making major changes or analyzing blast radius.

48 stars 10 forksOther Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add sethdford/claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add sethdford/claude-skills --skill change-impact-analysis
Manual install
git clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/architect/architecture-governance/skills/change-impact-analysis ~/.claude/skills/change-impact-analysis

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Change Impact Analysis

Systematically analyze impacts of architectural changes to predict risk and plan safe rollout.

## Context

You are analyzing impact of a major change. Trace affected systems, identify risks, plan mitigation. Read current dependency graph, deployment practices, system health metrics.

## Domain Context

Based on change management and impact analysis frameworks:

- **Direct Impact**: System directly modified. Code changes, performance changes, behavior changes.
- **Indirect Impact**: Dependent systems affected. Database schema change affects clients. Service API change affects all callers. Message format change affects consumers.
- **Risk Assessment**: What could go wrong? Cascading failures? Data loss? Performance regression? Unavailability of critical path?
- **Rollback Plan**: If change goes wrong, can you revert quickly? What data consistency issues might occur?

## Instructions

1. **Trace Dependencies**: What systems depend on the component you're changing? Use dependency graph tools (source analysis, API scanning). Interview teams.

2. **Assess Direct Impact**: For the component itself, what's changing? Behavior? Performance? Data model? How does change affect invariants, contracts, SLAs?

3. **Assess Indirect Impact**: For each dependent system, how does change affect it? Can they continue working with new interface? Will they need code changes? Testing?
Read the full skill on GitHub

Details

Skill name
change-impact-analysis
Path
architect/architecture-governance/skills/change-impact-analysis/SKILL.md
License
MIT
Repo updated
11 March 2026

FAQ

What does the Change Impact Analysis skill do?

Predict impacts of architectural changes on dependent systems. Trace dependencies, assess risk, plan rollout. Use when making major changes or analyzing blast radius.

How do I install the Change Impact Analysis skill?

Claude Code plugin: /plugin marketplace add sethdford/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Change Impact Analysis popular?

It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.

Related skills

Browse the most popular Claude skills, all other skills, or write your own with the skills generator.