鱼皮AI导航
鱼皮AI导航
  • 主页
  • 社区
  • AI工具
  • AI知识库
  • AI提示词
  • MCP
  • Skills
  • AI学习资源
  • AI资讯
  • GitHub开源
登录/注册

reviewing-changes

面向 Android 开发的代码审查辅助能力,能根据变更类型自动匹配对应检查清单,聚焦 MVVM 架构、Jetpack Compose 实践、Kotlin 语言规范及 Gradle 依赖管理,提供结构化、分阶段、上下文感知的深度审查建议。

测试与安全效率工具
访问 GitHub
文档Skills.MD
name
reviewing-changes
version
3.0.0
description
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.

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

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?

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

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?

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.md (focused review)
  • Feature Addition → checklists/feature-addition.md (comprehensive review)
  • UI Refinement → checklists/ui-refinement.md (design-focused review)
  • Refactoring → checklists/refactoring.md (pattern-focused review)
  • Infrastructure → checklists/infrastructure.md (tooling-focused review)

The checklist provides:

  • Multi-pass review strategy
  • Type-specific focus areas
  • What to check and what to skip
  • Structured thinking guidance

Step 4: Execute Review Following Checklist

Before diving into details: 1. What are the highest-risk areas of this change? 2. Which architectural patterns need verification? 3. What security implications exist? 4. How should I prioritize my findings? 5. What tone is appropriate for this feedback?

Follow the checklist's multi-pass strategy, thinking through each pass systematically.

Step 5: Consult Android Reference Materials As Needed

Load reference files only when needed for specific questions:

  • Issue prioritization → reference/priority-framework.md (Critical vs Suggested vs Optional)
  • Phrasing feedback → reference/review-psychology.md (questions vs commands, I-statements)
  • Architecture questions → reference/architectural-patterns.md (MVVM, Hilt DI, module org, error handling)
  • Security questions (quick reference) → reference/security-patterns.md (common patterns and anti-patterns)
  • Security questions (comprehensive) → docs/ARCHITECTURE.md#security (full zero-knowledge architecture)
  • Testing questions → reference/testing-patterns.md (unit tests, mocking, null safety)
  • UI questions → reference/ui-patterns.md (Compose patterns, theming)
  • Style questions → docs/STYLE_AND_BEST_PRACTICES.md

Core Principles

  • Appropriate depth: Match review rigor to change complexity and risk
  • Specific references: Always use file:line_number format for precise location
  • Actionable feedback: Say what to do and why, not just what's wrong
  • Efficient reviews: Use multi-pass strategy, skip what's not relevant
  • Android patterns: Validate MVVM, Hilt DI, Compose conventions, Kotlin idioms
测试与安全
效率工具

快捷安装

复制到终端去安装 Skill

npxskillsaddbitwarden/android--skill"reviewing-changes"
站长:程序员鱼皮 老鱼简历 商务合作 增值电信业务经营许可证
2026 鱼皮AI导航 | 沪ICP备19026706号-6
站长:程序员鱼皮 老鱼简历 商务合作 增值电信业务经营许可证
2026 鱼皮AI导航 | 沪ICP备19026706号-6
🔥热门工具
朱雀AI检测朱雀AI检测
朱雀AI检测助手朱雀AI检测助手
LovartLovart
老鱼简历老鱼简历
WritePass官网WritePass官网
面多多面多多
CursorCursor
星月写作星月写作
朱雀AI检测助手朱雀AI检测助手
零感AI零感AI
Skills 推荐
debug
debug 是一个系统化定位软件缺陷根因的技能,适用于用户报告 'fix'、'broken'、'error' 等问题或测试意外失败时。它通过可验证的假设、最小复现、因果链分析和回归测试,确保在修复前准确定位根本原因。
webapp-testing
提供本地 Web 应用的端到端测试能力,支持页面导航、元素交互、表单填写、动态等待、断言验证、截图捕获、浏览器日志收集及网络请求拦截,适用于前端功能验证与 UI 行为调试。
definition-of-done-generator
自动生成项目完成标准的规范定义与配置文件,提供符合企业级工作流要求的最佳实践指导,输出可直接投入生产环境的代码和验证结果,适用于需要标准化流程审批、合规审查及跨系统集成的复杂项目管理场景。
implement
实现 Linus Dashboard 的功能开发与集成,基于 TypeScript 和 Python 构建前后端组件,遵循严格的代码规范与架构模式,完成视图、卡片、服务及传感器等模块的创建与验证,确保高质量交付并兼容 Home Assistant 生态。
cloud-scheduler-job-creator
自动处理 Google Cloud Platform 中的云调度任务创建,提供符合最佳实践的配置方案与生产级代码生成,支持计算、存储、大数据及机器学习服务的集成部署。