Skip to content
Get packs

Change Impact Analysis

Maps what a planned code, data, or interface change will affect, then checks the finished diff against that plan.

Source Download skill
Repository
affaan-m/ECC
Stars
295,127
Licence
MIT
Files
2 files

What it does

Before an AI agent changes code, data, APIs, or governance docs, this skill makes it trace real dependencies (imports, calls, routes, schemas, tests, docs, deployment steps) and list what could break, marking anything it cannot prove as unverified. After the change, it compares the actual diff with that plan and reports scope creep or leftover risk. It is read-only by default and asks before writing files.

Great for

  • Engineers planning risky changes such as database migrations, authentication updates, or public API changes
  • Teams that need a written blast-radius check and rollback plan before a release
  • Reviewers who want to confirm an implemented change matches its original impact analysis

Skip it if

  • Small, isolated edits where a quick manual check is enough, since the process adds overhead
  • Projects without tests, docs, or version control history, because the skill relies on that evidence and will report many unverified items
  • Non-technical users looking for a general code review, since it focuses on dependency and release impact rather than style or logic bugs

Try asking

  • “Analyze the impact of changing the users API response format before I merge it”
  • “Review this database migration for compatibility, recovery, and irreversible effects”
  • “Compare my finished cross-module refactor with the original impact analysis and list unverified consumers”
  • “What is the blast radius if we change the authentication token format?”
Step-by-step guide: how to use Change Impact AnalysisInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 2 original files, the MIT licence and an attribution note.

    change-impact.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip change-impact.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip change-impact.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Give the agent the Spec or Issue describing the intended change so the post-implementation check has a baseline to compare against.
  • Ask for the impact analysis before any implementation starts, so unknowns can be resolved early.
  • Expect the agent to ask before writing a report file; name the location you want if your project has an impact or review folder.

What's inside

  • agents/openai.yaml
  • SKILL.md

Redistributed unmodified from affaan-m/ECC under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.