codebase-researcher

Locate implementations across multiple Android repositories by systematically exploring each sub-repo to find code, trace call flows, and map architecture. This provides exact file paths, line references, and cross-module citations for every finding.

Tracing call flows in unfamiliar multi-repo codebases requires systematic exploration to track references across modules like MSAL, Broker, Common, and ADAL. Evidence-based reporting provides explicit source attribution and exact line numbers for each traced path.

Evidence-based codebase research works by systematically locating architectural patterns and providing findings with exact file paths, line numbers, and contextual explanations. It acknowledges gaps and cites sources to aid cross-repo understanding and debugging.

Exploring project structure in Android codebases without prior knowledge is supported by systematically scanning all modules to locate feature implementations, references, and architecture. Findings include cross-module citations and explicit source attribution.

Find code for specific features across sub-repositories by identifying the target feature and beginning systematic exploration across all modules. This locates implementations, references, and architecture while providing exact file paths and line references.

Cross-module citations are needed when tracing call flows or locating implementations across multi-repo Android setups like MSAL, Broker, Common, and ADAL. They provide explicit source attribution and acknowledge gaps to aid cross-repo debugging.