Skill

code-flow-tracer

Traces code execution paths, data flows, and call graphs via /sourceatlas:flow queries. Reveals boundaries, entry points, cycles for understanding features and implementations.

developer-tools

npx claudepluginhub lis186/sourceatlas --plugin sourceatlas

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Trigger this skill when the user:

SKILL.md

Similar Skills

tracer

Traces execution paths, maps dependencies, follows data flows, and explores unfamiliar code systematically from entry points to build incremental understanding.

3 files

flow

trace

Traces feature, request, or data flows through codebase from entry points (API routes, UI handlers, jobs) to storage, documenting layers, transformations, side effects, and dependencies via graphs or grep.

1 file6 tools

universe

call-chain

242

Traces execution paths from entry points through code knowledge graph. Shows call chains with criticality scores and generates Mermaid flowcharts for flow analysis.

cartograph

Stats

Parent Repo Stars33

Parent Repo Forks1

Last CommitDec 23, 2025

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

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

Identify the feature, function, or flow the user wants to trace

Run /sourceatlas:flow "<query>" with a natural language description

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?"

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

Identify the feature, function, or flow the user wants to trace
Run /sourceatlas:flow "<query>" with a natural language description
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?"