lis186
@lis186
Public Skills
overview
by lis186
Get project overview - scan <5% of files to achieve 70-80% understanding
pattern
by lis186
Learn design patterns from the current codebase
history
by lis186
Smart temporal analysis using git history - Hotspots, Coupling, and Recent Contributors
deps
by lis186
Analyze dependency usage for library/framework/SDK upgrades
impact
by lis186
Analyze the impact scope of code changes using static dependency analysis
clear
by lis186
Clear saved SourceAtlas analysis results
list
by lis186
List saved SourceAtlas analysis results
flow
by lis186
Extract business logic flow from code, trace execution path from entry point
code-flow-tracer
by lis186
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
by lis186
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.
pattern-finder
by lis186
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.
dependency-analyzer
by lis186
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
by lis186
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
by lis186
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.