research-codebase

To research monorepo architecture, you can use an automated codebase exploration tool that spawns parallel sub-agents to analyze documentation, locate components, and find implementation patterns concurrently. This provides consolidated reports with file references and architectural insights.

The best way to find specific implementations across a codebase is to run a deep dive analysis that identifies framework packages and extension patterns. By analyzing code locations and documentation concurrently, it returns consolidated file references for targeted components like ProductFacade.

Parallelized codebase analysis works by spawning specialized sub-agents that investigate documentation, code locations, and patterns concurrently. It understands Package-First monorepo architecture principles, prioritizing framework packages to quickly map extension points and component relationships.

Yes, you can integrate Jira tickets into codebase exploration and architecture analysis. When explicitly requested, the research process supports Jira ticket integration alongside web research to contextualize component locations and implementation patterns within active development tasks.

Yes, codebase research works directly with Shopsys platform monorepos. The analysis is architecture-aware, specifically adhering to Shopsys's Package-First monorepo principles to prioritize framework packages and accurately identify extension patterns across the platform.

You need automated codebase research when you must quickly understand complex architecture, identify patterns, or find specific implementations across a large monorepo. It replaces manual code exploration by parallelizing documentation analysis and code location tasks to deliver consolidated architectural reports.