trace

Traces feature execution paths with file-and-line step-by-step flows.

71|7|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/mbwsims/claude-universe --skill trace-mbwsims
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trace
Source: https://github.com/mbwsims/claude-universe/tree/main/skills/trace
Command: npx skills add https://github.com/mbwsims/claude-universe --skill trace-mbwsims

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Understanding how a feature moves data through a codebase is time-consuming and error-prone when done manually. This Skill makes it straightforward to locate the entry point, follow calls across layers, and identify where data is transformed, validated, stored, or emitted so changes can be made safely.

Core Features & Use Cases

  • End-to-end tracing: Follow a feature from entry (route, UI action, job, or consumer) through handlers, services, and data access layers.
  • Dependency-graph assisted: Use a dependency graph to spot hubs, cycles, and downstream impact while minimizing manual grep work.
  • Observations & safety checks: Flag missing validation, error handling gaps, implicit dependencies, and test coverage as part of the trace.
  • Use case: Walk an API POST request from route to database to produce a concise flow diagram, file-and-line referenced step list, and a list of risky observations before a code change.

Quick Start

Trace the "checkout" feature from its entry route through every layer to the database and return a concise visual flow plus a detailed step-by-step report.

Frequently Asked Questions about trace

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

FAQPage Schema
How do I trace data flow through a codebase from an API endpoint to the database?

Tracing data flow from an API endpoint to the database involves following execution paths across handlers, services, and data access layers to map data transformations and side effects. This Skill automates that by producing file-and-line referenced step-by-step flows with layer classifications.

What is the best way to map execution paths for event-driven handlers and background jobs?

Mapping execution paths for event-driven handlers and background jobs requires tracking message consumers and cross-service data movement. This Skill traces these feature execution paths end-to-end to reveal where data is emitted, transformed, or stored.

Can I identify missing validation and error handling gaps while analyzing codebase architecture?

Identifying missing validation and error handling gaps during architecture analysis is achievable through dependency-graph assisted tracing. This Skill flags implicit dependencies and test coverage observations while mapping data flow.

How do I perform a security review using a dependency graph to spot cycles and downstream impact?

Performing a security review using a dependency graph helps spot architectural hubs, cycles, and downstream impact. This Skill utilizes dependency graphs to minimize manual grep work and trace feature execution paths safely.

Does this data flow tracing approach work for cross-service UI actions and message consumers?

Data flow tracing for cross-service UI actions and message consumers is fully supported by this Skill. It handles entry-to-storage analysis for UI actions, message consumers, and background jobs to produce concise visual flows.

When do I need to trace feature execution paths for a codebase change?

Tracing feature execution paths is needed before making codebase changes to understand how data moves and where side effects occur. This Skill provides detailed reports on validations, branch handling, and risky observations to ensure safe modifications.