SkillsAdd

smithery.ai

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.

First seen Mar 23, 2026

Installation

$ npx skills add https://smithery.ai
View on skills.sh ↗ Website ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

positioning-truth-tracer Similar name
aaron-he-zhu/aaron-marketing-skills

Use when the user asks to "check our positioning against what we can actually ship", "trace whi…

9 installs
doca-dpa-hl-tracer Similar name
nvidia/skills

Use this skill when the user runs doca_dpa_hl_tracer to capture/decode DPA-side traces at the p…

130 installs

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai
smithery-ai-cli 7.8K frontend-design 6.2K skill-creator 2.5K ck:ui-ux-pro-max 1.3K pdf 1.2K xlsx 966 pptx 894 docx 884 webapp-testing 1 web-design-reviewer 657

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,465 B
  • docs SUMMARY.md 225 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

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