Impact

Analyze the impact scope of code changes using static dependency analysis

49 stars 4 forksSoftware Development Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add lis186/SourceAtlas

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 lis186/SourceAtlas --skill impact
Manual install
git clone --depth 1 https://github.com/lis186/SourceAtlas.git /tmp/SourceAtlas
mkdir -p ~/.claude/skills
cp -r /tmp/SourceAtlas/plugin/commands/impact ~/.claude/skills/impact

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

From the SKILL.md

# SourceAtlas: Impact Analysis (Static Dependencies)

> **Constitution**: This command operates under [ANALYSIS_CONSTITUTION.md](../../../ANALYSIS_CONSTITUTION.md) v1.0
>
> Key principles enforced:
> - Article I: Structure over details (track dependencies, not implementation)
> - Article II: Mandatory directory exclusion
> - Article IV: Evidence format (file:line references)
> - Article VI: Scale awareness (limit tracking depth for large projects)

## Context

**Analysis Target:** $ARGUMENTS

**Goal:** Identify all code affected by changes to the target component through static dependency analysis.

**Time Limit:** Complete in 5-10 minutes.

---

## Quick Start

1. **Check cache** (if no `--force` flag) → See [reference.md#cache-behavior](reference.md#cache-behavior)
2. **Execute analysis** using [workflow.md](workflow.md)
3. **Verify output** using [verification-guide.md](verification-guide.md)
4. **Auto-save** to `.sourceatlas/impact/` → See [reference.md#auto-save](reference.md#auto-save)

---

## Your Task

You are **SourceAtlas Impact Analyzer**, specialized in tracing static dependencies and identifying change impact.

Help the user understand:
1. What code directly depends on the target
2. What code indirectly depends on it (call chains)
3. Which tests need updating
4. Migration checklist and risk assessment

---

## Core Workflow

Follow these high-level steps. For detailed instructions, see [workflow.md](workflow.md).
Read the full skill on GitHub

Details

Skill name
impact
Path
plugin/commands/impact/SKILL.md
License
MIT
Repo updated
22 October 2026

FAQ

What does the Impact skill do?

Analyze the impact scope of code changes using static dependency analysis

How do I install the Impact skill?

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

Is Impact popular?

It lives in lis186/SourceAtlas, which has 49 GitHub stars and 4 forks.

Related skills

Code Flow Tracer

49

lis186/SourceAtlas

Trace code execution paths and data flow. Use when user asks "how does X work", "what happens when X", "trace the flow of X", "where does data come from", or needs to understand feature implementation.

Software Development

Codebase Overview

49

lis186/SourceAtlas

Quickly understand a new codebase's architecture, tech stack, and patterns. Use when user asks "what is this project", "project overview", "how is this codebase structured", "what tech stack", or when onboarding to a new codebase.

Software Development

Dependency Analyzer

49

lis186/SourceAtlas

Analyze dependencies for upgrade planning and migration. Use when user asks "upgrade to X", "migrate from X to Y", "what breaks if we upgrade", "iOS 17 migration", "React 18 upgrade", or planning framework/SDK upgrades.

Productivity & Notes

Impact Analyzer

49

lis186/SourceAtlas

Analyze what code will be affected by changes. Use when user asks "what will break if I change X", "impact of changing X", "dependencies of X", "is it safe to modify X", or before making significant code changes.

Software Development

History Analyzer

49

lis186/SourceAtlas

Analyze git history for hotspots, coupling, and knowledge distribution. Use when user asks "who knows this code", "what files change most", "hotspots", "bus factor", "knowledge silos", or needs to understand code evolution.

Software Development

Pattern Finder

49

lis186/SourceAtlas

Find implementation examples and design patterns in the codebase. Use when user asks "how to implement X", "how does this project do X", "show me examples of X", "where is X implemented", or needs to follow existing code conventions.

Software Development

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