Android-specific code review checklist and MVVM/Compose pattern validation for Bitwarden Android — use this for any review task, even if the user doesn't explicitly ask for a "checklist". Detects change type automatically and loads the right review strategy (feature additions, bug fixes, UI refinements, refactoring, dependency updates, infrastructure). Triggered by "review PR", "review changes", "review this code", "check this code", "Android review", code review requests on Kotlin/ViewModel/Composable/Repository/Gradle files, or any time someone asks to look at a diff, PR, or code changes in bitwarden/android.
This skill provides Android-specific workflow additions that complement the base bitwarden-code-reviewer agent standards.
IMPORTANT: Work systematically through each step before providing feedback. Each checklist file includes structured thinking guidance for its review passes.
Retrieve any additional information linked to the pull request using available tools (JIRA MCP, GitHub API).
If pull request title and message do not provide enough context, request additional details from the reviewer:
Android metadata checks — flag as ❓ if any of these are missing:
*Screen.kt or Composable changes but has no screenshotsViewModel or Repository but has no test plan or test file changesUse the base change type detection from the agent, with Android-specific refinements:
Android-specific patterns:
ViewModel, new Repository, new @Composable functions, new *Screen.kt files*Screen.kt, *Composable.kt, ui/ package files.github/workflows/, gradle/, build.gradle.kts, libs.versions.tomllibs.versions.toml or build.gradle.kts with version bumpsBased on detected type, read the relevant checklist file:
checklists/dependency-update.md (expedited review)checklists/bug-fix.md (focused review)checklists/feature-addition.md (comprehensive review)checklists/ui-refinement.md (design-focused review)checklists/refactoring.md (pattern-focused review)checklists/infrastructure.md (tooling-focused review)The checklist provides:
Follow the checklist's multi-pass strategy, thinking through each pass systematically.
Load reference files only when needed for specific questions:
reviewing-incremental-changes agent skill; scope to changed lines only, do not flag new issues in unchanged codereference/priority-framework.md (Critical vs Suggested vs Optional)reference/review-psychology.md (questions vs commands, I-statements)reference/architectural-patterns.md (MVVM, Hilt DI, module org, error handling)reference/security-patterns.md (common patterns and anti-patterns)docs/ARCHITECTURE.md#security (full zero-knowledge architecture)reference/testing-patterns.md (unit tests, mocking, null safety)reference/ui-patterns.md (Compose patterns, theming)docs/STYLE_AND_BEST_PRACTICES.mdfile:line_number format for precise location