explore

Read-only codebase exploration uses tools like grep, glob, and semantic search to analyze file-level implementations and architecture safely. It inspects components and navigates large projects without modifying the repository, producing a concise, actionable summary of how components interact.

The best way to locate component implementations across large projects is using pattern-based search and semantic search. By querying specific modules, you can locate file definitions, trace call graphs, and generate contextual summaries explaining how components interact and depend on each other.

Yes, you can use grep and glob to navigate call graphs in a read-only repository. These pattern-based search tools locate files, definitions, and dependencies, allowing you to investigate modules and answer architecture questions without modifying the codebase.

Semantic search works effectively for understanding module dependencies in large codebases. It supports architecture analysis by locating relevant files and definitions, enabling you to trace how components interact and depend on each other to produce a concise, actionable summary.

To generate a contextual summary of component interactions, use read-only exploration with semantic search and pattern matching. Investigate specific modules to trace call graphs and dependencies, which produces a concise explanation of how the architecture fits together.

You should not use read-only codebase exploration when you need to modify, refactor, or write code, as it strictly requires read-only access to the repository. It is designed solely for answering architecture questions and understanding how components work without altering the codebase.