Guides Android code reviews with type-specific checklists and MVVM/Compose pattern validation. Use when reviewing Android PRs, pull requests, diffs, or local changes involving Kotlin, ViewModel, Composable, Repository, or Gradle files. Triggered by "review PR", "review changes", "check this code", "Android review", or code review requests mentioning bitwarden/android. Loads specialized checklists for feature additions, bug fixes, UI refinements, refactoring, dependency updates, and infrastructure changes.
View on GitHubFebruary 2, 2026
Select agents to install to:
npx add-skill https://github.com/NeverSight/skills_feed/blob/1c090ee8fabe780233397e095aaff8f759320e88/data/skills-md/bitwarden/android/reviewing-changes/SKILL.md -a claude-code --skill reviewing-changesInstallation paths:
.claude/skills/reviewing-changes/# Reviewing Changes - Android Additions This skill provides Android-specific workflow additions that complement the base `bitwarden-code-reviewer` agent standards. ## Instructions **IMPORTANT**: Use structured thinking throughout your review process. Plan your analysis in `<thinking>` tags before providing final feedback. ### Step 1: Retrieve Additional Details <thinking> Determine if more context is available for the changes: 1. Are there JIRA tickets or GitHub Issues mentioned in the PR title or body? 2. Are there other GitHub pull requests mentioned in the PR title or body? </thinking> 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: - Link a JIRA ticket - Associate a GitHub issue - Link to another pull request - Add more detail to the PR title or body ### Step 2: Detect Change Type with Android Refinements <thinking> Analyze the changeset systematically: 1. What files were modified? (code vs config vs docs) 2. What is the PR/commit title indicating? 3. Is there new functionality or just modifications? 4. What's the risk level of these changes? </thinking> Use the base change type detection from the agent, with Android-specific refinements: **Android-specific patterns:** - **Feature Addition**: New `ViewModel`, new `Repository`, new `@Composable` functions, new `*Screen.kt` files - **UI Refinement**: Changes only in `*Screen.kt`, `*Composable.kt`, `ui/` package files - **Infrastructure**: Changes to `.github/workflows/`, `gradle/`, `build.gradle.kts`, `libs.versions.toml` - **Dependency Update**: Changes only to `libs.versions.toml` or `build.gradle.kts` with version bumps ### Step 3: Load Appropriate Checklist Based on detected type, read the relevant checklist file: - **Dependency Update** → `checklists/dependency-update.md` (expedited review) - **Bug Fix** → `checklists/bug-fix.
Issues Found: