trace

Trace execution flow from entry points into Mermaid diagrams and Markdown summaries.

5|3|Updated Jun 18, 2024
One-click install
npx skills add https://github.com/Unique-AG/ai --skill trace-unique-ag
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trace
Source: https://github.com/Unique-AG/ai/tree/main/.claude/skills/trace
Command: npx skills add https://github.com/Unique-AG/ai --skill trace-unique-ag

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Mapping execution flow from an entry point to produce diagrams and summaries reduces code comprehension time and helps identify dependencies and side effects.

Core Features & Use Cases

  • Mermaid flow diagrams showing function call graphs with external dependencies highlighted
  • Structured Markdown summary including call chains, key files, side effects, ambiguities, and truncations
  • Language-agnostic semantic tracing with depth control and focus-question support

Quick Start

Run the trace tool with an entry point, e.g., /trace path/to/file.py or a function/class name to generate a diagram and narrative.

Frequently Asked Questions about trace

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

FAQPage Schema
How do I generate a call graph from a specific function entry point?

You can trace execution flow by providing a file path, function, or class name as an entry point. It returns a Mermaid call graph diagram and a Markdown summary highlighting external dependencies and side effects.

Does semantic code tracing work across different programming languages?

Yes, semantic tracing operates language-agnostically by analyzing code semantics rather than relying on specific language tooling, allowing it to map execution flow across different programming environments.

How can I map code execution flow and identify external dependencies?

You can map execution flow by running the trace tool with an entry point. It outputs a Mermaid diagram and a comprehensive narrative that reveals the call graph, external dependencies, and side effects.

What is the default depth limit for tracing a function call graph?

The default depth limit for tracing a call graph is 3 levels from the specified entry point. This depth controls how deep the execution flow mapping traverses before returning the diagram and narrative.

How are ambiguous or external calls handled during code analysis?

During code analysis, ambiguous or external calls are flagged within the structured Markdown summary. The trace narrative explicitly documents these calls as truncations or ambiguities rather than failing.