codebase-exploration

You can explore an unfamiliar codebase safely by using read-only search tools like glob and grep to locate files and analyze structures without risking accidental modifications. This approach allows quick discovery of functions and architectures while maintaining efficiency and safety.

The best way to search for code implementations across modules is using pattern-based file discovery with glob and grep for lightweight searches, then following import chains and checking configs to map relationships for deep understanding of the architecture.

Yes, you can trace feature implementations without full reads by using grep to find specific code snippets and targeted reads to analyze only relevant sections, ensuring token-efficient tool usage while enforcing strict no-modification rules.

Yes, read-only codebase analysis works for understanding architectural relationships by following import chains, checking configs, and mapping dependencies to trace how features connect across modules while maintaining a strict no-modification safety boundary.

You should avoid using glob and grep for codebase exploration when you need to modify code, as these tools enforce strict read-only rules; they are designed specifically for locating files and analyzing structures without making changes.