Prepare a Rabby Mobile publish PR from a clean branch by bumping the `apps/mobile` version, running `yarn rnversion`, creating a default changelog when missing, committing `build: publish <version>`, and opening a GitHub PR when `gh` is available. Use when…
Use when choosing, writing, reviewing, or reorganizing Rabby Mobile tests; deciding between unit, JS integration, Hermes device integration, and E2E coverage; defining mock boundaries; or adding test-related CI.
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…
Assess every Rabby Mobile change for runtime performance impact, with deeper review for startup, unlock/account state, Home, stores, hooks, navigation, lists, I/O, native boundaries, or background work. Use during pull-request review and before handing off…
Review or change Rabby Mobile startup stages, module loading, lock/unlock routing, keyring runtime readiness, visible/current account state, first-Home readiness, service/store hydration, or startup-sensitive work without regressing correctness or JS-thread…
Use when adding deterministic non-production testing, typed behavior injection, lifecycle observation, or future performance instrumentation to a Rabby Mobile Screen, reusable component, or local feature boundary while preserving production behavior and…
Promote one or more committed changes onto the Thursday tmp branch, push the result without disturbing the current worktree, and dispatch the Feature Test GitHub Actions workflow. Use when Codex needs to merge a fix into `tmp/YYYYMMDD`, especially the current…
Use when changing Rabby Mobile database write paths, resource sync persistence, TypeORM/op-sqlite executeBatch/upsert code, app-data-source reset, clear-cache behavior, or Android performance work involving JS-to-native database writes.