slax-review

To review Kotlin Multiplatform Compose PRs for platform correctness, you must validate commonMain logic alongside Android and iOS platform code, checking networking, serialization, and data-sync layers for platform-specific pitfalls before merging.

Catching Compose UI state recomposition performance issues requires analyzing recomposition patterns through parallel sub-agent scanning and cross-checking findings against known issues via web research to identify architecture regressions before they land.

Validating commonMain logic and platform-specific code simultaneously is supported by running parallel sub-agent scanning across Android and iOS platform code, ensuring networking and serialization layers maintain correctness across both platforms.

The best way to cross-check pull request review findings against known dependency issues is using targeted dependency research with WebSearch and WebFetch, combined with a Codex second opinion to reconcile differences in the final report.

Kotlin Multiplatform PR review needs interactive developer clarification when requirements or behavior are unclear, using dialogue-based questioning to capture accurate context and intent before proceeding with targeted dependency and syntax research.

You should not use an automated multi-stage review workflow for pull requests that do not touch commonMain logic, platform code, networking layers, or Compose UI state, as the structured investigation and parallel scanning offer no relevant platform correctness validation.