jason0404 Run a comprehensive Android review for the user's provided scope, current changes, crash trace or requested build/flavour.
Workflow
- Determine the requested review scope from the user prompt or current git diff.
- Use the relevant Android specialist agents to inspect the scope:
android-correctness-reviewerfor Kotlin correctness and runtime behavior.android-lifecycle-reviewerfor lifecycle, Glide, callbacks, leaks and crash paths.android-build-release-reviewerfor Gradle, manifests, flavours and production delivery risks.android-resource-reviewerfor XML, Compose resources, localization and visible brand text.
- Run only the specialist agents relevant to the actual scope. For a general pre-release or pull-request review, run all four.
- Consolidate their findings, remove duplicates and retain only evidence-backed findings.
- Produce a clear risk/release recommendation and focused verification checklist.
- Mandatory final step: invoke the
android-html-report-generatoragent with the consolidated findings, scope, validation steps and release recommendation. This final stage must write a standalone HTML report underandroid-review-reports/.
Rules
- Never generate the final HTML report before specialist analysis is completed.
- Do not omit the final HTML report unless file-writing permission is explicitly denied.
- If report writing is denied, still provide the consolidated review result and clearly say that the HTML file could not be created.
- Do not claim a build/test passed unless it was actually run successfully.
- Treat secrets, tokens and credentials as sensitive and redact them in the report.
Final response format
Report:
- Review status and highest risk.
- Agents/tasks completed.
- HTML report output path.
- Build/test verification performed or still required.