mode-trace

Trace code execution to reveal call sequences and data transformations.

3|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/benegessarit/skill-composer --skill mode-trace
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mode-trace
Source: https://github.com/benegessarit/skill-composer/tree/main/skills/mode-trace
Command: npx skills add https://github.com/benegessarit/skill-composer --skill mode-trace

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps users understand and follow how code executes by tracing the call sequence, data flow, and control paths from entry points to outcomes, making debugging and architecture comprehension easier.

Core Features & Use Cases

  • Trace execution paths across modules to reveal call graphs and data transformations.
  • Identify bottlenecks and misrouted calls by inspecting function-level flow.
  • Use during code reviews or when onboarding new developers to understand a codebase's runtime behavior.

Quick Start

Provide a trace of the execution path for the given entry point to reveal the call order and data transformations.

Frequently Asked Questions about mode-trace

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

FAQPage Schema
How do I trace code execution paths across multiple modules?

Tracing code execution paths involves inspecting function calls, data transformations, and control flow from entry points to outcomes. This requires tooling to inspect function calls and data structures, outputting clear step-by-step data state transitions across modules.

What is the best way to debug misrouted function calls and identify bottlenecks?

Debugging misrouted calls and bottlenecks requires tracing function-level execution flow. By inspecting the precise sequence of calls and data transformations, you can identify exactly where control paths deviate or performance degrades.

Can I use execution tracing to understand a new codebase during developer onboarding?

Execution tracing is highly effective for developer onboarding. It maps runtime behavior and call sequences across modules, helping new developers understand how data transforms from entry points to outcomes without manually reading code linearly.

Does code tracing work for understanding architecture during code reviews?

Code tracing works well for architecture understanding during code reviews. It reveals the underlying call graph and control flow lineage, allowing reviewers to verify data transformations and path logic across multiple modules.

Why does my data flow analysis not show correct state transitions during debugging?

Data flow analysis may miss state transitions if the trace lacks sufficient tooling to inspect data structures at each step. Accurate debugging requires capturing the exact data state and control flow lineage from entry point to outcome.