explore-codebase

Codebase exploration involves analyzing directory structures, configuration files, and representative code samples to map project architecture, identify naming conventions, and document module interactions before making modifications.

The best way to map project structure and dependencies is to analyze directory layouts to identify entry points, modules, and configuration files, clarifying how modules interact and which interfaces are critical.

Yes, you can assess test coverage by reviewing existing test suites to identify tested areas and those needing attention, ensuring you understand current test patterns before modifying critical modules.

Modifying code without understanding software architecture introduces bugs because you remain unaware of existing dependency interactions, error handling strategies, and critical module interfaces, leading to broken conventions and unexpected failures.

Yes, you need to check the directory structure before modifying critical modules to identify entry points, configuration files, and representative code samples, ensuring complete context awareness of project patterns.