菜单
Use when reviewing mobile code changes — check for lifecycle issues, memory leaks, thread safety, and platform-specific pitfalls.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/ArisGuimera/MobiAI-Core --skill mobiai-review-code命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | mobiai-review-code |
| description | Use when reviewing mobile code changes — check for lifecycle issues, memory leaks, thread safety, and platform-specific pitfalls. |
| license | MIT |
| compatibility | ["claude-code","cursor","copilot","codex"] |
| platforms | ["android","ios","kmp","flutter","react-native"] |
Perform a mobile-specific code review, checking for common issues that static analysis tools miss.
The Graph indexes Kotlin/Swift symbols across the repo, so callers of any symbol modified in the diff can be located instantly. Used during Step 3 (Review Checklist) and Step 4 (Verify Test Coverage) to detect call sites and tests that the diff may have missed.
If <repo>/.mobiai/graph/index.json exists:
# Freshness — if "hace Xd" with X ≥ 1, suggest refresh (don't auto-run):
mobiai graph status
# For each symbol modified/renamed in the diff, find callers outside the diff:
mobiai graph callers <SymbolFromDiff>
mobiai graph search <OldSymbolName>
The callers list surfaces call sites that the diff may not have updated — a common source of silent breakage when the PR is partial.
If the index is ≥1 day old:
"El índice del Graph es de hace Xd. Si la rama tiene cambios recientes, considerá
mobiai graph initantes de revisar."
Don't run init autonomously.
If .mobiai/graph/index.json does not exist and the project has .kt or .swift files:
"No veo el índice del Graph. Generalo con
mobiai graph initpara que pueda detectar callers fuera del diff."
Don't run init autonomously.
Skip silently when:
Determine the target branch this change will be merged into:
gh pr view --json baseRefName --jq '.baseRefName' — this is the authoritative answergh repo view --json defaultBranchRef --jq '.defaultBranchRef.name'Then generate the diff against that branch:
BASE_BRANCH="<the branch from above>"
git diff "$BASE_BRANCH"...HEAD
Why this matters: If you diff against the wrong branch, you'll report hundreds of false changes that belong to the base branch, not to this PR. The user will see a noisy, useless review.
@RequiresApi or checks Build.VERSION.SDK_INT?[weak self] where needed?!) on values that could be nil?sceneDidEnterBackground / applicationWillTerminate?build() methods?useMemo, useCallback, React.memo?useEffect return?Platform.OS checks where needed?Check if the changed code has tests. This is a separate step — do not skip it.
src/test/ or src/androidTest/ that test the same classes_test.dart files matching the changed files.test.js / .test.tsx filesAlways include a "Test coverage" section in your review output, even if tests are present. State what you found.
Structure your review as:
When the user responds to your review: