gitnexus-exploring

To trace execution flows, you query indexed repository context for relevant processes and deep-dive key symbols to map callers, callees, and step-by-step execution paths. This provides a structured map of how specific end-user request paths like authentication or payments operate.

Navigating codebase architecture involves discovering high-level context first, then querying for specific execution flows and tracing process resources. This method guides you from broad repository indexing down to concrete symbol deep-dives for complete architecture understanding.

Mapping incoming and outgoing calls for a specific symbol requires querying indexed context to retrieve related processes and end-to-end traces. This symbol deep-dive reveals the exact execution requirements and dependencies connected to the target function.

Yes, you need an active indexed repository context to trace execution paths. If the index is stale, the system detects it and instructs you to run the analyze command to refresh the codebase data before querying flows.

Yes, you can trace webhook handling processes by querying for execution flows related to the concept and reading the process resources. This follows the step-by-step execution requirements and maps the full end-to-end request path.