task-use-research-code-strategy

To trace data flow across files, you investigate the codebase architecture by specifying your goals, starting points, and desired output structure. This read-only analysis identifies patterns, dependencies, and ownership boundaries to map feature implementation.

Analyzing feature implementation end-to-end without modifications requires read-only codebase investigation. You provide a starting point and desired output structure, allowing the analysis to map the flow from API gateway to database and identify relevant functions.

Yes, codebase exploration locates recurring patterns, dependencies, and ownership boundaries. By specifying your investigation goals and starting points, the analysis maps feature implementation and data flow across multiple files without altering the source.

To start a code analysis on a complex project, you must specify your investigation goals, starting points, and desired output structure. This ensures the read-only exploration effectively maps architecture, data flow, and feature implementation.

Yes, code strategy investigation supports identifying dependencies across files. It facilitates read-only codebase exploration to understand architecture and data flow, mapping how features like user authentication are handled end-to-end.