codebase-exploration

Map implementation context in a new project by running read-only investigations that trace authentication or feature logic across the repository, gathering evidence from exact file paths and git history without modifying files.

Yes, you can verify implementation facts against source code safely by running read-only investigations that gather evidence from exact file paths and git history, ensuring no files or configurations are modified during the analysis.

Map data and config flow across a repository by tracing logic paths and identifying key abstractions through read-only investigation, producing structured summaries driven by concrete file paths to document how the system moves data.

Codebase exploration supports git history review to confirm implementation facts, allowing you to verify how features were built by cross-referencing current source code structure against historical commit evidence without modifying the repository.

You should avoid automated codepath tracing when you need to modify files or configurations, as this approach is strictly read-only and designed for investigation, evidence gathering, and mapping rather than active development or refactoring.