Find Compose stability and recomposition issues

Proprietary

Search-only recipes that surface Jetpack Compose anti-patterns the Android docs and Compose stability guide call out: unstable parameter types, mutable classes annotated @Stable/@Immutable, inline Modifier allocations, missing remember keys, effect-handler misuse, navigation inside composable bodies, single-child layout wrappers, lazy-list items without keys, and API-shape violations. Each match is a SearchResult for human review — Compose remedies are judgement calls (hoist? wrap? annotate? split?) that depend on context outside any one expression. For diff-only output on the small autofix set, use ImproveKotlinCompose.

org.openrewrite.kotlin.compose.Compose$KtRecipe
mod run . --recipe='org.openrewrite.kotlin.compose.Compose$KtRecipe'

Install it once from Recipe actions, then run it on every repository under the current directory. New to the Moderne CLI? Set it up.

Recipe list

It runs these recipes, in this order.

  1. Find Compose stability issues
  2. Find Compose Modifier smells
  3. Find Compose layout hierarchy smells
  4. Find Compose state read/write issues
  5. Find Compose remember key issues
  6. Find Compose effect handler issues
  7. Find Compose navigation / coroutine misuse
  8. Find Compose API design issues
  9. Find Compose ViewModel wiring issues
  10. Find Compose Modifier ordering smells
  11. Find Modifier.padding(...) shorthand opportunities
  12. Find Compose state + remember misuse
  13. Find Compose effect-handler misuse
  14. Find Compose recomposition smells
  15. Find lifecycle-naive flow / LiveData collection in Composables
  16. Find Compose function-naming conventions
  17. Find hardcoded color literals inside @Composable
  18. Find remember { mutableStateOf(emptyList/Map()) } candidates for snapshot-aware containers
  19. Find single-child wrapper composables (Material 3)