rabby-mobile-code-review

Review Rabby Mobile pull requests for actionable correctness, wallet-safety, security, privacy, performance, build, and supply-chain issues, and publish validated inline GitHub findings. Use for outbound review of a PR or its changed code; use mobile-pr-ready-watch instead to mark a PR ready, monitor incoming feedback, implement requested fixes, or resolve review threads.

Jump to install

Repository: RabbyHub/rabby-mobile
Last source activity: August 6, 2026 at 08:13
Detected SKILL.md language: English
Stars: 77
Forks: 37

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/RabbyHub/rabby-mobile --skill rabby-mobile-code-review

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

2 files

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

Rabby Mobile Code Review

Review the current PR head and report only actionable issues. Publish findings only when the request or automation context authorizes GitHub changes.

This skill authors outbound review findings. For making a PR ready, watching reviewer feedback, applying requested fixes, or resolving addressed threads, use skills/mobile-pr-ready-watch/SKILL.md.

Review Workflow

Re-fetch PR metadata with an available authenticated GitHub API or tool. Continue only when the PR is open and not a draft. Record the current head SHA.

Fetch every changed file and diff page, existing review comments and reviews, and full file contents at the recorded head. Read AGENTS.md, CLAUDE.md, skills/rabby-mobile-performance-review/SKILL.md, relevant specialist playbooks, and touched package, native, build, and workflow configuration.

Build a changed-line map from the diff. Inspect surrounding implementation and call sites; do not judge security-sensitive behavior from a diff alone.

Report only issues introduced or made newly reachable by the PR. Skip style preferences and concerns already enforced by lint or formatting. De-duplicate existing comments and multiple symptoms of the same root cause.

Anchor every public finding inline to a valid changed diff line. Use the right side for additions and the left side for deletions. Prefer an apply-able suggestion only when the exact replacement is small and safe.

Use REQUEST_CHANGES only for blocking wallet-safety, correctness, build, data-loss, or demonstrated critical-path performance defects. Use for actionable non-blocking findings.