pr-review-checklist
Use when asked to review a PR, propose review comments, or prepare a merge checklist.
When & Why to Use This Skill
This Claude skill streamlines the Pull Request (PR) workflow by providing an automated, high-standard review checklist. It focuses on code correctness, architectural integrity, and Android-specific optimizations, helping teams maintain code quality and accelerate the merge process through structured feedback.
Use Cases
- Automating the identification of logic errors, edge cases, and threading issues during Pull Request reviews.
- Ensuring Android-specific best practices are met, including Jetpack Compose state safety and structured concurrency with Coroutines.
- Generating prioritized review comments categorized by severity (must, should, nit) to provide clear guidance for developers.
- Creating comprehensive merge-ready checklists that verify unit tests, architectural boundaries, and documentation completeness before deployment.
| name | pr-review-checklist |
|---|---|
| description | Use when asked to review a PR, propose review comments, or prepare a merge checklist. |
Review checklist
Correctness
- Does the change match the issue/user story?
- Edge cases, nullability, threading, lifecycle.
Tests
- New/updated unit tests exist for logic changes
- Flaky patterns avoided (timers, real network, device state)
Architecture
- Boundaries respected (UI/Domain/Data)
- DI scope correct
- Side effects isolated
Android specifics
- Compose: state hoisting, recomposition safety, stable types
- Coroutines: dispatcher correctness, structured concurrency
- Resources: localization, accessibility
Deliverable
- 5-10 review comments grouped by severity: [must] [should] [nit]
- A merge-ready checklist (tests, docs, rollout notes)