android-pr-review

Review Android pull requests for Kotlin and architecture quality issues.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/soygabimoreno/Los-ANDROIDES --skill android-pr-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: android-pr-review
Source: https://github.com/soygabimoreno/Los-ANDROIDES/tree/main/.agents/skills/android-pr-review
Command: npx skills add https://github.com/soygabimoreno/Los-ANDROIDES --skill android-pr-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you review Android pull requests and quickly spot issues that can break user experiences or degrade the codebase, such as bugs, architecture regressions, and insufficient test coverage.

Core Features & Use Cases

  • Bug and regression detection: Prioritizes user-visible failures so problems are caught before merging.
  • Clean Architecture and boundary checks: Flags architecture violations that undermine maintainability.
  • Test quality and coroutine/Compose risk review: Identifies missing or weak tests and common Kotlin/Android concurrency, Flow, and lifecycle hazards.
  • Use Case: Review a PR that changes audio playback or data flow and ensure it keeps MVVM/Clean Architecture boundaries intact, has appropriate tests, and doesn’t introduce threading or Compose state problems.

Quick Start

Use the android-pr-review skill to review the pull request diff against AGENTS.md and produce a severity-ordered checklist of findings with file/line references and actionable fixes.

Frequently Asked Questions about android-pr-review

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

FAQPage Schema
How do I review an Android pull request for architecture and coroutine issues?

You can review Kotlin pull requests by analyzing diffs against AGENTS.md to detect Clean Architecture violations, coroutine/Flow threading hazards, and Jetpack Compose state issues, yielding a severity-ordered checklist with file/line references and concrete fixes.

What is the best way to catch Jetpack Compose state and lifecycle problems in a PR?

To catch Jetpack Compose state problems in a PR, analyze UI state diffs to flag lifecycle hazards and threading issues, prioritizing user-visible failures and providing actionable fixes before the code merges.

Can I use this approach to check Gradle configuration and dependency changes?

Yes, you can check Gradle configuration and dependency changes by applying the review process to build files, identifying configuration risks and dependency issues that could degrade the codebase or slip past CI.

Does Android PR review work with Clean Architecture and MVVM boundaries?

Yes, Android PR review works with Clean Architecture and MVVM boundaries by checking diffs for layer violations, ensuring data flow changes maintain separation of concerns, and flagging architecture regressions that undermine maintainability.

How to ensure adequate test coverage for Kotlin Flow and coroutine changes?

To ensure test coverage for Kotlin Flow and coroutine changes, review the PR diff to identify missing or weak tests, checking concurrency behavior and lifecycle hazards, and producing a severity-ordered checklist of findings.

Why does my Android CI pipeline miss coroutine threading and architecture regressions?

Android CI pipelines miss coroutine threading and architecture regressions because they lack context on Clean Architecture boundaries and Compose lifecycle hazards, requiring a targeted PR diff review against AGENTS.md standards to catch these issues.