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.
Install
/plugin marketplace add lis186/SourceAtlasThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add lis186/SourceAtlas --skill code-flow-tracergit clone --depth 1 https://github.com/lis186/SourceAtlas.git /tmp/SourceAtlas
mkdir -p ~/.claude/skills
cp -r /tmp/SourceAtlas/plugin/skills/code-flow-tracer ~/.claude/skills/code-flow-tracerPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Code Flow Tracer ## When to Use Trigger this skill when the user: - Wants to understand how a feature works end-to-end - Asks what happens when an action is triggered - Needs to trace data flow through the system - Asks "how does X work" - Asks "what calls X" or "what does X call" ## Instructions 1. Identify the feature, function, or flow the user wants to trace 2. Run `/sourceatlas:flow "<query>"` with a natural language description 3. Returns call graph, boundary detection, and flow visualization ## Query Formats - Feature flow: `/sourceatlas:flow "user login"` - Function trace: `/sourceatlas:flow "handleSubmit"` - Error paths: `/sourceatlas:flow "error handling flow"` - Data origin: `/sourceatlas:flow "where does userProfile come from"` - Reverse trace: `/sourceatlas:flow "who calls validateToken"` ## What User Gets - Call graph visualization (ASCII tree) - Boundary detection (API, DB, LIB, CLOUD markers) - Recursion and cycle detection - Entry points identification - 11 analysis modes available ## Example Triggers - "How does the login flow work?" - "What happens when user clicks submit?" - "Trace the checkout process" - "Where does this data come from?" - "Who calls this function?"
Details
- Skill name
code-flow-tracer- Repository
- lis186/SourceAtlas
- Path
plugin/skills/code-flow-tracer/SKILL.md- License
- MIT
- Repo updated
- 22 October 2026
FAQ
What does the Code Flow Tracer skill do?
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.
How do I install the Code Flow Tracer 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 Code Flow Tracer popular?
It lives in lis186/SourceAtlas, which has 49 GitHub stars and 4 forks.
Related skills
Codebase Overview
49lis186/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.
Dependency Analyzer
49lis186/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.
Deps
49lis186/SourceAtlas
Analyze dependency usage for library/framework/SDK upgrades
C4 Codebase Architecture
24lmammino/c4-codebase-architecture-skill
Helps an agent inspect a repository and produce C4 architecture documentation. Use this when reverse engineering a codebase, documenting system context, containers, components, or clarifying architecture from code and infrastructure.
Uw Unity Debugging
47devdavv/unity-ai-workflow
Systematic 4-phase debugging framework for Unity projects with GameDebug wrapper generation. Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes. Triggers on requests like "this doesn't work", "there's a bug", "it crashes when", "fix this error", "why is this happening", "null reference exception", "test is failing", "unexpected behavior", "something broke", or any debugging task. Four-phase framework (gather evidence, isolate, hypothesize, fix) that ensures understanding before attempting solutions.
History Analyzer
49lis186/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.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.