b2c-android-analyze-module

To analyze an Android module's ViewModel and screen structure, pass the module name to parse Kotlin sources from the feature or core folders, identifying BaseIntentViewModel inheritance, UiState fields, and navigation maps to generate a structured onboarding report.

Mapping Kotlin codebase patterns like apiFlow and slackFlow is done by scanning the module's init blocks and ViewModel inheritance structures, which produces a concise summary of API usage and core design behaviors for code review.

Yes, you can generate documentation for core Android modules lacking PRD notes because the analysis parses Kotlin sources directly to map structure and link to PRD notes if they are present, outputting a report regardless.

Android module structure analysis works for both feature and core directory layouts by parsing Kotlin sources specifically from the feature/ARGUMENTS or core/ARGUMENTS paths to identify components like Screens, ViewModels, and Contracts.

Identifying cross-module references and test status across Android ViewModels requires parsing the module's Kotlin sources to detect UiState fields, navigation maps, and test configurations, resulting in a structured analysis report.

Automated module analysis accelerates understanding of Kotlin source files by instantly mapping BaseIntentViewModel inheritance, init blocks, and navigation maps, reducing manual effort compared to reading code line by line for documentation.