lis186/SourceAtlas

history

Smart temporal analysis using git history - Hotspots, Coupling, and Recent Contributors

impact

Analyze the impact scope of code changes using static dependency analysis

overview

Get project overview - scan <5% of files to achieve 70-80% understanding

pattern

Learn design patterns from the current codebase

list

List saved SourceAtlas analysis results

reset

Clear saved SourceAtlas analysis results

deps

Analyze dependency usage for library/framework/SDK upgrades

flow

Extract business logic flow from code, trace execution path from entry point

code-flow-tracer

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.

codebase-overview

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.

dependency-analyzer

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.

history-analyzer

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.

impact-analyzer

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.

pattern-finder

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.