A Claude Code plugin with skills for React Native apps: fixing failing iOS and Android builds, safely upgrading Expo SDK and React Native, decoding Hermes crashes, handling deep links, and running EAS builds and store releases.
Claude Code
> /plugin marketplace add AnilBurcu/claude-code-react-native> /plugin install rn@claude-code-react-native
Codex
$ npx skills add AnilBurcu/claude-code-react-native -a codex
Cursor
$ npx skills add AnilBurcu/claude-code-react-native -a cursor
Gemini CLI
$ npx skills add AnilBurcu/claude-code-react-native -a gemini-cli
GitHub Copilot
$ copilot plugin marketplace add AnilBurcu/claude-code-react-native$ copilot plugin install rn@claude-code-react-native
OpenCode
$ npx skills add AnilBurcu/claude-code-react-native -a opencode
Windsurf
$ npx skills add AnilBurcu/claude-code-react-native -a windsurf
Claude knows React. It doesn't know why your pod install just failed.
A Claude Code plugin that adds the React Native knowledge you only get from shipping apps: build failure triage, SDK upgrades that don't eat a weekend, Hermes crash decoding, push notification debugging, subscription pipelines and store submission checklists.
Claude Code is genuinely good at React Native application code. Where it struggles is the layer underneath: the Gradle log with the real error buried at line 400, the OTA update that bricks old binaries because the runtime fence moved, the sandbox subscription that expires mid-test, the push token that belongs to a different delivery service than the one you sent through.
That knowledge lives in the heads of people who shipped apps and got burned. This plugin writes it down in a form Claude loads exactly when it's needed. Each skill is a distilled runbook, not a doc dump: what breaks, in what order to check, and which fixes are safe.
Inside Claude Code:
/plugin marketplace add AnilBurcu/claude-code-react-native
/plugin install rn@claude-code-react-native
That's it. The knowledge skills activate on their own when your conversation touches their territory. The workflow skills are yours to invoke.
To try it from a clone without installing anything:
git clone https://github.com/AnilBurcu/claude-code-react-native
claude --plugin-dir ./claude-code-react-native/plugins/rn
Tested with Claude Code 2.1. The skill listing costs about 1,200 tokens of
descriptions per turn (/skill-doctor shows the exact figure on your
machine); a skill's full text loads only when it is used.
These activate automatically when the task matches. You never call them; Claude reads them when your build fails or your crash report is unreadable.
| Skill | Kicks in when |
|---|---|
native-build-errors | pod install, Gradle, Xcode or linker failures |
expo-sdk-upgrade | upgrading Expo SDK / React Native, post-upgrade breakage |
new-architecture | Fabric, TurboModules, codegen errors, library compatibility |
hermes-crashes | minified stack traces, Sentry symbolication, SIGSEGV, ANRs |
push-notifications | FCM / APNs setup, tokens, notifications that never arrive |
in-app-purchases | RevenueCat, sandbox weirdness, webhooks, entitlement design |
supabase-mobile-auth | native Apple / Google sign-in, session refresh, RLS from mobile |
rn-performance | slow lists, re-renders, janky animations, startup time |
eas-release | build profiles, OTA update safety, store submission |
deep-linking | universal links / app links, AASA and assetlinks traps, cold-start links |
monorepo-metro | workspace apps, duplicate react-native, hoisting, EAS in monorepos |
patching-libraries | patch vs fork vs replace decisions, patch hygiene across upgrades |
log-triage | pulling the one error line out of thousand-line build and device logs |
| Command | What it does |
|---|---|
/rn:fix-build [ios|android] | reproduces the failing build, finds the first real error, fixes it, rebuilds to verify |
/rn:upgrade-sdk [version] | guided SDK upgrade with preflight, changelog review and both-platform verification |
/rn:new-arch-check | audits every dependency for New Architecture support and abandonment risk |
/rn:perf-audit [path] | sweeps the code for the performance antipatterns that actually cost milliseconds |
/rn:prep-release [platform] | pre-submission audit: versioning, OTA fence, permissions, secrets, store policy |
Subagents keep multi-round investigations out of your main conversation:
| Agent | Use for |
|---|---|
build-doctor | build failures that need several rounds of log digging |
crash-analyst | production crash reports, from minified trace to root cause |
perf-auditor | read-only performance sweeps of larger codebases |
release-checker | full pre-submission verification with evidence |
Say the Android build breaks after you add a camera library. Without the
plugin, the usual loop is generic: clean caches, delete node_modules, hope.
With native-build-errors loaded, Claude captures the log to a file, greps
for the deepest Caused by: instead of reading the last line, quotes the
actual error (say, a minCompileSdk mismatch in AAR metadata), applies the
smallest fix for that class of failure, and rebuilds to verify before
declaring anything solved.
Same shape everywhere else: sandbox subscriptions expiring mid-test get read as normal sandbox behavior instead of a bug hunt, and an OTA publish after a native change gets stopped at the runtime fence instead of shipping a crash to your existing users.
The skills follow the open Agent Skills format, so they work outside Claude Code too. The skills CLI finds all of them in this repo:
npx skills add AnilBurcu/claude-code-react-native
Pick the ones you want and it installs them for the agents it detects.
You can also use any skill fully by hand: copy its folder from
plugins/rn/skills/ into ~/.claude/skills/ (personal) or
.claude/skills/ (per project). The agents go into ~/.claude/agents/
the same way.
There's also a CLAUDE.md template with the project rules that prevent the expensive mistakes (npx expo install over npm install, never hand-editing generated native folders, the OTA rule). Copy what applies, delete the rest.
The bar for a PR: it happened to you in a real project. This repo is field notes, not documentation coverage, and it stays useful only if every line earns its place. Fixes for things that changed in newer SDK or store policy versions are especially welcome.
Keep the writing plain. Short sentences, no marketing adjectives, name the exact error strings people will search for.
Stars on GitHub
A development methodology for coding agents that makes the agent brainstorm before building, follow plans, run parallel work and finish branches in a disciplined way. You get fewer skipped steps and more consistent results from your coding assistant.
@obraHelps you take a change from a rough idea or bug report through to a tested, reviewed result, with each step handled by a focused skill. Its skills cover pinning down domain terms, designing module interfaces, diagnosing hard bugs, and reviewing changes against your repo's coding standards.
@mattpocockGives your coding agent a planning, testing and review routine to follow on every task. It plans before building, checks changes with tests, has a fresh reviewer look for regressions, and saves repeated wins as reusable skills.
@affaan-mDeveloper tools for working on the React codebase itself. Provides skills for extracting error messages, managing and debugging feature flags across release channels, running Flow type checks, and fixing lint and formatting issues before committing.
@facebookA Claude Code plugin with skills for React Native apps: fixing failing iOS and Android builds, safely upgrading Expo SDK and React Native, decoding Hermes crashes, handling deep links, and running EAS builds and store releases. Install it with the command on its page. It includes deep-linking, eas-release, expo-sdk-upgrade. Its skills do not fire on their own yet. Free and open source.
Is this plugin yours?
Claim it with GitHubSubmit a pluginPromote it