android-code-review

Detects critical Android Kotlin code quality problems in app stability and maintainability.

2|Updated May 12, 2026
One-click install
npx skills add https://github.com/youfengknight/Android-Code-Skills --skill android-code-review-youfengknight
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: android-code-review
Source: https://github.com/youfengknight/Android-Code-Skills/tree/main/py-claude-marketplace-py-plugin-skills-android-code-review
Command: npx skills add https://github.com/youfengknight/Android-Code-Skills --skill android-code-review-youfengknight

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps you identify high-impact problems in Kotlin-based Android code that can cause crashes, memory leaks, and architecture drift.

Core Features & Use Cases

  • Critical bug detection: Flags memory leaks, coroutine/lifecycle leaks, and lifecycle violations that can lead to ANR or crashes.
  • Architecture & pattern enforcement: Ensures MVVM/MVI integrity, correct UIState usage, and proper separation between View, ViewModel, UseCases, and Repositories.
  • Actionable fixes: Produces a structured report with what to fix and how, including corrected code examples.

Quick Start

Ask: review android code for the Kotlin files you provide, focusing on critical and high-priority issues only.

Frequently Asked Questions about android-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect memory leaks and lifecycle issues in Kotlin Android code?

To detect memory leaks in Kotlin Android code, review ViewModels and Fragments for improper coroutine scope usage. This flags lifecycle violations and unsafe Flow collection that cause ANR or crashes.

How do I enforce MVVM architecture and single UIState patterns in Android?

Enforcing MVVM architecture and single UIState patterns requires checking Kotlin source files for correct separation between View, ViewModel, UseCases, and Repositories. This ensures proper business-logic placement and maintainable code.

Can I review an Android PR diff for critical architecture problems?

Yes, you can review an Android PR diff to find critical architecture problems. The review applies to PR diffs focusing on ViewModels, Activities, Fragments, UseCases, and Repositories to identify high-priority architecture drift.

What is the best way to find architecture drift in Kotlin repositories and UseCases?

The best way to find architecture drift in Kotlin repositories and UseCases is to scan source code for correct business-logic placement and naming violations. This enforces MVVM/MVI integrity and identifies separation of concerns issues.

How do I fix Android coroutine and Flow lifecycle violations after detection?

To fix Android coroutine and Flow lifecycle violations after detection, follow a structured report detailing what to fix and how. This report includes corrected Kotlin code examples for lifecycle-safe Flow and coroutine usage.