architecture-reviewer

Start by inventorying modules, dependencies, and the version catalog, then read one representative feature slice from UI to data layer. Evaluate modularization, layering, DI, state management, error handling, and testing, then rank findings by severity, effort, and risk.

Check module cohesion and feature-module isolation, separation of UI, domain, and data layers, consistent state management with StateFlow, DI scoping correctness, Result-based error handling, coroutine discipline, and test coverage across layers.

Yes, it includes a KMP-specific axis covering the commonMain/androidMain/iosMain split, iOS-facing API type safety, and use of SKIE or KMP-NativeCoroutines for Flow and suspend interoperability.

Linters catch style and local code issues, while this review forms architectural opinions with reasoning and severity rankings. It evaluates cross-cutting patterns like module dependency direction and state management consistency that static analysis cannot judge.

Skip it for single pull request reviews, which should be reviewed directly. It is designed for module-level or whole-app scope where patterns repeat across many files, not isolated changes.