菜单
Build the Android APK for the mobile app by running npm run android:apk. Use when the user asks to generate, build, or produce an Android APK / release / install file for apps/mobile.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Deep code review of a diff across both Orbit repos against one shared rubric, orchestrating the five review subagents and a backward-compat guard. Use when the user asks to review a PR, file, folder, or staged changes in orbit-ui-mobile or orbit-api. Replaces /review and /security-review.
Get an independent cross-model second opinion (GLM-5.2 via opencode) on a specific, load-bearing technical claim or a Critical code-review finding — a different model reads the claim + code and returns AGREE / DISAGREE / UNSURE. Use to stress-test a single Critical finding, a risky assertion, or a close call before you commit to it. Auto-fired inside /pr-review on each Critical finding that survives the skeptic. Not for open-ended research (use /deep-research) or multi-lens judgement (use /llm-council).
Break a PRD into GitHub issues across orbit-ui-mobile + orbit-api
Answer an open-ended "what's the best way to…?" question with orchestrated multi-agent deep web research. Decompose the question, fan out narrow research subagents in parallel, verify the load-bearing claims adversarially, iterate to saturation, then synthesize ONE opinionated, source-backed, decision-ready recommendation. Orbit-aware (dual-repo stack, solo-dev cost calibration). Use for technology/vendor choices, architecture & tooling decisions, cost comparisons, migration approaches, or best-practice questions — anything whose answer needs current external evidence beyond the codebase. Not for code edits, single-fact lookups, or questions answerable from the repo alone.
Create implementation plan with cross-repo codebase analysis
Prime agent with Orbit project context (both repos + optional GitHub issue)
| name | android-generate |
| description | Build the Android APK for the mobile app by running npm run android:apk. Use when the user asks to generate, build, or produce an Android APK / release / install file for apps/mobile. |
Runs the project's existing Android APK release command.
The APK bakes in EXPO_PUBLIC_API_BASE at prebuild time, so the API the build targets is decided by the environment present when the script runs. Default (no env set) builds against prod (https://api.useorbit.org).
This local build always uses Google TEST AdMob ad units (never real ads) and skips the Sentry source-map upload (which requires the CI-only SENTRY_AUTH_TOKEN), so QA installs never serve live ads and the build never fails on a missing Sentry token. Real-ad production releases — with source maps uploaded to Sentry — ship only through the .github/workflows/android-release.yml CI workflow, which injects the real AdMob IDs + Sentry token and guards against shipping test units.
npm run android:apk -w @orbit/mobile. The android:apk script is defined in the apps/mobile workspace (node scripts/android-release-apk.js), not at the root, so it must be targeted with -w @orbit/mobile.