skills.rest
lis186
lis186COMMUNITY
Explore all skills by this author →
GitHub

code-flow-tracer

Trace code execution paths and data flow across modules, APIs, and services.

46|4|Updated Nov 19, 2025
Search Tags:#debugging#trace#flow#code-analysis#call graph#data-provenance
One-click install
npx skills add https://github.com/lis186/SourceAtlas --skill code-flow-tracer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-flow-tracer
Source: https://github.com/lis186/SourceAtlas/tree/main/plugin/skills/code-flow-tracer
Command: npx skills add https://github.com/lis186/SourceAtlas --skill code-flow-tracer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables developers to understand complex code paths by tracing end-to-end execution flow and data movement across modules, APIs, and services.

Core Features & Use Cases

  • End-to-end flow tracing: generate call graphs and data propagation paths for a feature or function.
  • Boundary detection: identify API, DB, LIB, and CLOUD boundaries in the flow.
  • Debugging aid: visualize recursion, cycles, and entry points to pinpoint the root cause.
  • Use Case: Imagine diagnosing how a user action such as "checkout" triggers database writes and API calls across services.

Quick Start

Use the code-flow-tracer by issuing the /sourceatlas:flow "<description of flow>" command to generate a call graph and flow analysis.

Frequently Asked Questions about code-flow-tracer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I trace code execution paths across modules and services?▼

To trace code execution paths across modules and services, you can issue a natural language query using the /sourceatlas:flow command to generate a call graph and flow analysis for your described feature.

What is the best way to debug data flow across APIs and databases?▼

Debugging data flow across APIs and databases is done by generating a call graph that detects API, DB, LIB, and CLOUD boundaries, which helps pinpoint the root cause of complex cross-service issues.

Can I visualize recursion and cycles during a code analysis trace?▼

Yes, you can visualize recursion, cycles, and entry points during code analysis to pinpoint the root cause of an issue by generating an end-to-end execution flow graph for your function.

How do I check data provenance for a specific feature like checkout?▼

To check data provenance for a feature like checkout, trace the execution flow to generate a call graph and data propagation path showing how user actions trigger database writes and API calls.

Does the code flow tracer require specific dependencies or components?▼

No specific dependencies or components are required to use the code flow tracer, as it operates by accepting natural language queries to return call graphs, boundary detection, and flow analysis results.

Related Skills

Explore More Software Engineering Skills→
uyelikaniluyelikanil

perfetto-sql

Convert natural language requests into Perfetto SQL queries for trace analysis.

Community
Advanced
vietlinhh02vietlinhh02

Root Cause Tracing

Trace errors backward through the call chain to identify root causes.

Community
Intermediate
iiammaeiiammae

audit-augmentation

Map SARIF and weAudit findings onto Trailmark code graphs for security audits.

Community
Advanced
InfinityBowmanInfinityBowman
3

Observability Analysis

Audit production observability stacks for logging, tracing, metrics, alerting, and debuggability.

Community
Advanced