bee:explore-codebase

To map an unfamiliar codebase for architecture discovery, you need a two-phase exploration process that first identifies natural perspectives like layers and components, then dispatches adaptive deep-dive explorers to synthesize actionable insights.

Feature understanding across a codebase requires autonomous exploration that traces interdependencies and component mapping, ensuring you comprehensively grasp how specific features work without missing critical structural details.

Autonomous codebase exploration prevents costly debugging mistakes by actively countering excuses to skip discovery, ensuring you map relevant code sections and interdependencies completely before making complex changes.

Yes, you can use codebase exploration to plan complex changes in a new project by discovering underlying structures and synthesizing findings into actionable insights, preventing incomplete understanding of component interdependencies.

You need architecture discovery on your codebase when starting a new project or debugging a complex issue, requiring a comprehensive map of relevant code sections to ensure you do not miss critical architectural details.

Manual codebase exploration for component mapping risks incomplete understanding and costly mistakes, whereas an autonomous two-phase approach systematically discovers natural perspectives and performs adaptive deep-dives to reveal underlying structures.