mobile-code-review
/mobile-code-review
Reviews mobile code for production bugs across Flutter, native Android, native iOS, React Native and Kotlin Multiplatform, including KMP source-set and host API contracts. Covers lifecycle, concurrency, UI state and native boundaries with file:line evidence. Use for a code review, PR, project audit, quality check or /reis-mobile:review.
- Author
- wrsilva ↗
- Repository
- reis-mobile ↗
- Licence
- MIT
- Last repository change
- 13.10.2026
Assessment and security
- Files in this package
- 10
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 13.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Reviews mobile code for production bugs across Flutter, native Android, native iOS, React Native and Kotlin Multiplatform, including KMP source-set and host API contracts. Covers lifecycle, concurrency, UI state and native boundaries with file:line evidence. Use for a code review, PR, project audit, quality check or /reis-mobile:review.
Original author description
Reviews mobile code for production bugs across Flutter, native Android, native iOS, React Native and Kotlin Multiplatform, including KMP source-set and host API contracts. Covers lifecycle, concurrency, UI state and native boundaries with file:line evidence. Use for a code review, PR, project audit, quality check or /reis-mobile:review.
How it works
- 1. Pick the checklists
- 2. Scope
- 3. Evidence before findings
- 4. What always matters, on any stack
- 5. Severity
- Report
SKILL.md preview
--- name: mobile-code-review description: Reviews mobile code for production bugs across Flutter, native Android, native iOS, React Native and Kotlin Multiplatform, including KMP source-set and host API contracts. Covers lifecycle, concurrency, UI state and native boundaries with file:line evidence. Use for a code review, PR, project audit, quality check or /reis-mobile:review. intents: [review, performance] stacks: ["*"] --- # Mobile Code Review One review process for every mobile stack. This file holds how to review and what always matters; each platform's checklist lives in its reference. ## 1. Pick the checklists Detect the stack first, then apply the platform checklist to the files in scope: | Project | Read | |---|---| | Flutter / Dart | [references/flutter.md](references/flutter.md), which orders the Flutter checklists in `references/flutter/` | | Native Android (Kotlin/Java), or the Android side of Kotlin Multiplatform | [references/android.md](references/android.md) | | Native iOS (Swift/Objective-C) | [references/ios.md](references/ios.md) | | React Native or Expo | [references/react-native.md](references/react-native.md) | | Kotlin Multiplatform shared and target changes | [references/kotlin-multiplatform.md](references/kotlin-multiplatform.md) | In a cross-platform app, native code in `android/`, `ios/` or native modules gets the native checklist too. Security findings follow `mobile-security` when it is loaded. ## 2. Scope - **Changes (diff or pull request):** review what changed, reading the whole file when the hunk is not enough to understand it. New untracked files are not in the diff; read them. - **Whole project:** start at the entry points (app startup, navigation, dependency setup), then the data layer, authentication and the most complex screens. ## 3. Evidence before findings - Open the code and confirm every suspicion. A finding without evidence at `file:line` does not go in the report. - Do not invent APIs, versions or lint rules. Check the lock files and build files (`pubspec.lock`, version catalog, `Package.resolved`, `package.json`) before claiming something is missing, deprecated or unavailable. - Do not report style that a configured linter already enforces. - When the project deliberately does something differently and it is coherent, say so instead of flagging it. ## 4. What always matters, on any stack - **Lifecycle:** async work that outlives its screen; listeners, subscriptions, timers and controllers never released. - **Threading:** I/O or heavy parsing on the main/UI thread; UI updated off it. - **State:** impossible states that can be represented; loading and error handled; state lost on rotation, backgrounding or process death. - **Network:** timeouts, retries without backoff, offline handling, unvalidated responses. - **Credentials:** tokens in insecure storage, secrets in code or the bundle, sensitive data in logs. - **Platform:** permissions requested without handling denial; manifest, `Info.plist`, entitlements or config changes that affect store publishing. - **Tests:** new logic without tests when the project already has a suite. ## 5. Severity Rank by real impact on users: crash or data loss, credential leak, store rejection, then noticeable degradation, then maintainability. Say why each finding matters, not only what rule it breaks. ## Report Unless an agent defines its own format, answer with: ```markdown ## Summary Stack, scope (diff or project), verdict: approve | approve-with-changes | request-changes. ## Critical ## Bugs ## Architecture ## Security ## Performance ## Maintainability ## Suggested changes Prioritized list. For each item: file:line, problem, why it matters, fix. ``` Write "No findings." in a section with nothing to report.
Files in this package (10)
- SKILL.md 4 KB
- references/android.md 5 KB
- references/flutter.md 2 KB
- references/ios.md 5 KB
- references/kotlin-multiplatform.md 1 KB
- references/react-native.md 5 KB
- references/flutter/pr-review.md 3 KB
- references/flutter/project-audit.md 4 KB
- references/flutter/static-analysis.md 5 KB
- references/flutter/widget-review.md 4 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · wrsilva/reis-mobile | 100 | MIT |
| owasp/secure-agent-playbook | 90 | CC-BY-4.0 |
Database snapshot: 13.11.2026 · package version ca2c8309460e (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100mobile-architecture
Designs and reviews mobile architecture across Flutter, native Android, native iOS, React Native and Kotlin Multiplatform. Covers state ownership, data flow, modules, dependency boundaries, navigation, offline data and KMP shared source sets versus host apps. Use when… - 100mobile-detect-stack
Detects the mobile stack of the current project (Flutter, Android, iOS, React Native, Kotlin Multiplatform), its languages and target platforms, using the reis-mobile detector. Use when you need to know which mobile stack a project uses before reviewing, debugging or changing… - 90mobile-kotlin-multiplatform
Use this skill when the user says 'Kotlin Multiplatform', 'KMP', 'Compose Multiplatform', 'shared Kotlin', 'KMP module', 'expect/actual', 'commonMain', 'KMP project', 'multiplatform library'. Build cross-platform mobile apps with Kotlin Multiplatform sharing business logic,… - 100mobile-dev
Use when the work is a mobile app in Flutter, React Native, Android (Kotlin), or iOS: architecture, state management, navigation, platform channels, widget or device tests, or app store readiness. - 90native-mobile-developer
Native Mobile Developer (/ios, /android) — builds true native apps: iOS with Swift/SwiftUI and Android with Kotlin/Jetpack Compose. Use when implementing native iOS or Android features, SwiftUI/Compose UI, platform APIs (notifications, camera, background, widgets), App… - 100mobile-dev
Build, run, and debug mobile apps - Expo, React Native, Flutter, native Android (Kotlin/Java, Gradle, Jetpack Compose) and native iOS (Swift, Xcode). Detect the stack, doctor the toolchain, start the packager or Gradle/xcodebuild, fix build errors, and ship UI changes. Use for…