kotlin-android-reviewer_skill

Overview

This skill reviews Android Kotlin projects for Jetpack Compose patterns, Coroutines/Flow usage, ViewModel structure, memory leaks, and performance issues. It focuses on practical, actionable recommendations to improve UI correctness, state management, and coroutine safety. Use it to get a prioritized list of issues and concrete fixes for Compose, Coroutines, Flow, and ViewModel code.

How this skill works

The reviewer scans project metadata (Android Gradle plugin, AndroidManifest, source dirs) and inspects Kotlin sources for anti-patterns and risky constructs. It detects Compose issues (unremembered objects, side-effects in composables, missing keys), coroutine misuses (GlobalScope, missing dispatchers, exception handling), Flow patterns (direct collect in composables, nullable StateFlow), ViewModel smells (context/view refs, missing SavedStateHandle), and common memory leaks. Results are returned as a categorized report with severity levels and recommended code changes.

When to use it

• Performing a code review on an Android Kotlin repo using MVVM/Clean Architecture
• Validating Jetpack Compose UIs for recomposition and state correctness
• Auditing coroutine and Flow usage for dispatcher, scope, and error handling issues
• Checking ViewModel design for unidirectional state and leak risks
• Investigating memory leaks, unremoved listeners, or unreleased bitmaps

Best practices

• Prefer stateless Composables and hoist state to parents; use remember and derivedStateOf where appropriate
• Use structured concurrency: viewModelScope/lifecycleScope and explicit Dispatchers (IO/Default)
• Collect Flows in the UI with collectAsState or produceState; provide concrete initial StateFlow values
• Avoid passing Activity/View references into ViewModel; use ApplicationContext or DI-provided resources
• Use sealed UiState + events for unidirectional data flow and expose StateFlow/LiveData read-only

Example use cases

• Automated pre-merge review of Compose screens to flag missing remember, LaunchedEffect misuse, and LazyColumn key omissions
• Security/robustness sweep to replace GlobalScope uses and add dispatcher separation and exception handling
• Refactor checklist for ViewModel conversion to UiState pattern and SavedStateHandle integration
• Memory leak audit to find inner classes holding Activity references, unremoved listeners, un-cancelled coroutine jobs, and unreleased bitmaps