Skip to content
cccskills
FreePublished on GitHub

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.

The English summary is being prepared. Showing the original description.

See how to install

Files included (10)

  • SKILL.md3.7 KB
  • references/android.md5.0 KB
  • references/flutter.md1.6 KB
  • references/flutter/pr-review.md3.4 KB
  • references/flutter/project-audit.md3.9 KB
  • references/flutter/static-analysis.md4.7 KB
  • references/flutter/widget-review.md3.5 KB
  • references/ios.md4.5 KB
  • references/kotlin-multiplatform.md1.3 KB
  • references/react-native.md4.5 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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:

ProjectRead
Flutter / Dartreferences/flutter.md, which orders the Flutter checklists in references/flutter/
Native Android (Kotlin/Java), or the Android side of Kotlin Multiplatformreferences/android.md
Native iOS (Swift/Objective-C)references/ios.md
React Native or Exporeferences/react-native.md
Kotlin Multiplatform shared and target changesreferences/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:

## 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.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Audits and fixes mobile accessibility across Flutter, native Android, native iOS, React Native and Kotlin Multiplatform, including shared Compose UI and native hosts. Covers TalkBack/VoiceOver labels, roles, state, reading order, touch targets, text scaling, contrast and focus. Use for a11y audits, screen-reader bugs or accessible UI implementation.

The English summary is being prepared. Showing the original description.

wrsilva/reis-mobile7Updated Oct 14, 2026

Builds native Android apps with the Android team's guides — Jetpack Compose UI, adaptive layouts, edge-to-edge, Compose styles, migrating XML views to Compose, Navigation 3 and predictive back; Android Gradle Plugin 9 upgrades, R8 keep rule analysis, profiling with Android Studio and Perfetto, and the Android CLI; Google Play policy compliance, Play Billing upgrades and the Engage SDK; Credential Manager restore and verified email; CameraX and Media3 Cast; App Functions and the ML Kit GenAI Prompt API; Wear OS, Android TV and display glasses. Use when writing, upgrading or auditing native Android (Kotlin) code for any of these topics, even if the user does not name the library.

The English summary is being prepared. Showing the original description.

wrsilva/reis-mobile7Updated Oct 14, 2026

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 structuring a feature, choosing state management, refactoring layers or deciding where a real class or screen belongs.

The English summary is being prepared. Showing the original description.

wrsilva/reis-mobile7Updated Oct 14, 2026

Implements and reviews mobile identity and session flows across Flutter, Android, iOS, React Native and Kotlin Multiplatform. Use for sign-in, passkeys, account recovery, provider linking, reauthentication, logout and concurrent refresh. Security audits belong to mobile-security; account deletion belongs to mobile-privacy.

The English summary is being prepared. Showing the original description.

wrsilva/reis-mobile7Updated Oct 14, 2026

Diagnoses build and runtime failures across Flutter, native Android, native iOS, React Native and Kotlin Multiplatform. Covers pub/Dart, Gradle/AGP, Xcode/CocoaPods, Metro, KMP source sets and iOS frameworks, crashes and deep links. Use for failing builds, app launches, stack traces or /reis-mobile:debug.

The English summary is being prepared. Showing the original description.

wrsilva/reis-mobile7Updated Oct 14, 2026

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 it, or when the user asks "what stack is this project?".

The English summary is being prepared. Showing the original description.

wrsilva/reis-mobile7Updated Oct 14, 2026

See all skills by wrsilva

Report a problem with this skill