What problem does it solve? When debugging a feature, developers often cannot tell which functions actually execute, which SQL statement writes a row, or which outbound HTTP request carries the data. This Skill produces a verified, execution-ordered map from the entry point down to the literal SQL statement and outbound METHOD /path?query, with accurate relative file:line references ready to paste into a debugger. ## Core Features & Use Cases - Verified call trees: Enumerates every caller at every chain level, re-derives line numbers from the working tree, and resolves dynamic dispatch to the concrete wired implementation. - Wire-level leaves: Quotes the actual SQL statement shape with binds and the literal outbound HTTP request with query params, envelope decoding, and auth source. - Structured output template: Produces entry-point tables, aligned call trees rendered via scripts/render_tree.py, outbound API and SQL tables, fork notes, and 5-8 suggested breakpoints. - Use Case: Ask "where do I set breakpoints to watch the checkout flow charge a card" and receive an ordered tree from the POST route through the payment gateway to the exact Stripe API call and the INSERT statement that records it. ## Quick Start Ask the assistant to trace the call path for a specific endpoint, cron job, or CLI command and list the breakpoints needed to step through it.
