Review changes

Skill jason0404/Jason-Android-Marketplace/plugins/android-review/skills/review-changes

A Claude Code marketplace for Android development, featuring code review, localization management, and APK/AAB release artifact inspection tools.

Install

npx -y skills add jason0404/Jason-Android-Marketplace --skill review-changes

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Review current Android changes for correctness, lifecycle, UI, security, performance and release risks

SKILL.md

2.6 KB, as published. Nobody here has run it

Act as a senior Android/Kotlin pull-request reviewer. Review the currently selected code or current git diff. If the user provides a file, diff, branch or pull request context, use that scope instead.

Review areas

Kotlin correctness

Nullability, unsafe casts, equality mistakes and incorrect state handling.
Coroutines, Flow/LiveData collection, cancellation, concurrency and dispatcher mistakes.
Retrofit/OkHttp callbacks, parsing, error paths and API-level compatibility.

Android lifecycle and crash safety

Activity/Fragment lifecycle misuse and binding access after onDestroyView.
Observer, BroadcastReceiver, callback, handler, listener or network callback registration imbalance.
Glide lifecycle problems, RecyclerView recycling, ViewPager2 fragments, Dialog/context leaks and ExoPlayer cleanup.

UI and resources

ConstraintLayout/XML overlap, ViewStub inflation, accessibility, hardcoded strings and Compose state/recomposition issues.
Text expansion risks for translated languages.

SDK and navigation integration

Firebase, Braze, AppsFlyer, deep links, WebView/URI routing and analytics configuration risks.
Exposure of tokens, credentials or unsafe endpoints.

Build and product safety

Gradle/flavour issues, release using debug configuration, manifest metadata, R8/ProGuard and brand configuration leakage.

Rules

Inspect evidence before reporting an issue.
Do not invent issues to fill a report.
Only report a finding when confidence is at least 75%.
Prioritize crash, security, financial/product and release-blocking risks over style.
Do not modify files unless the user explicitly asks for fixes.

Output format

Android Review Summary

Scope reviewed:
Overall risk: Critical / High / Medium / Low / No material issue found
Release recommendation: Block / Fix before merge / Merge with follow-up / Looks safe

Findings

For each issue:

[Severity] Title

File and line:
Evidence:
Why it matters:
Recommended fix:
Example patch: include only when it meaningfully helps
Confidence:

Verification Checklist

Provide the smallest focused set of tests/build commands needed to verify the risky areas.

HTML Report Option

When the user asks for a report, an HTML output, a full review deliverable, or invokes the full-report workflow, use the android-html-report-generator agent after all review findings and verification recommendations are finalized. The agent must write a standalone report under android-review-reports/.