code-flow-tracer
/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.
- Author
- lis186 ↗
- Repository
- SourceAtlas ↗
- Licence
- MIT
- Last repository change
- 21.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 21.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
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.
Triggers from the description
Original author description
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 it works
- When to Use
- Instructions
- Query Formats
- What User Gets
- Example Triggers
SKILL.md preview
--- name: code-flow-tracer description: 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. --- # 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?"
Versions
The database has no other skills named code-flow-tracer.
Database snapshot: 13.11.2026 · package version acd6c03e1de9 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100tracer
Use when tracing execution paths, mapping dependencies, understanding unfamiliar code, following data flow, investigating end-to-end behavior, debugging call chains, or deciding which files to read next. - 90trace
Traces a piece of code to every place its flow starts and down to the data it touches, including calls made from inside installed packages. Use when the user says "trace X", "trace this", "what calls this", "where is this used", "how does this request flow", or "where does this data come from". - 100hk-follow-breadcrumb
Consults existing breadcrumb analysis docs before exploring the codebase. Use this skill whenever the user asks about how a flow works, where something happens in the code, how to debug or test a specific area, what files are involved in a feature, or needs to understand the… - 90codemap
Trace one flow through a codebase and write it as a cited markdown map (Mermaid diagram plus stages with steps, reads and writes). Use when the user asks how a flow, feature or system works in a repo ("how does X work", "trace X", "map what happens when Y"), or wants a flow doc… - 100trace-data-flow
Trace actual data flow through an existing software project from input through validation, transformation, persistence, retrieval, and output. Use when asked to follow a field, calculation, endpoint, feature, or business operation, explain where an output came from, or compare… - 100researching-code
Use this skill when the user asks an architectural or semantic question about a codebase — phrases like "how does X work?", "what's the architecture?", "help me understand this codebase", "find all components that use Y", "trace the data flow from A to B", "where is feature Z…