# Assess React Native Migration

Assesses whether and how an existing mobile product should migrate to React Native.

- Repository: https://github.com/callstackincubator/agent-skills (1694 stars)
- Category: Mobile
- License: MIT
- Last updated: 2026-10-08
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add callstackincubator/agent-skills --skill assess-react-native-migration -g -a claude-code -y`
Codex: `npx skills add callstackincubator/agent-skills --skill assess-react-native-migration -g -a codex -y`
Cursor: `npx skills add callstackincubator/agent-skills --skill assess-react-native-migration -g -a cursor -y`
Gemini CLI: `npx skills add callstackincubator/agent-skills --skill assess-react-native-migration -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add callstackincubator/agent-skills`

## Description

Assesses whether and how an existing mobile product should migrate to React Native. Use when auditing one or more product repositories for migration readiness, including products whose iOS, Android, and other clients live in separate directories or repositories; choosing brownfield, greenfield, or a checkpoint-based path; defining a representative trial; or preparing a baseline and ROI decision before implementation. When product scope or material evidence is unavailable, grills the stakeholder with exactly one question per turn instead of sending a questionnaire.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Assess React Native Migration

Produce a read-only migration decision. Diagnose the product and delivery system; do not execute the migration.

## Establish Product Scope

Run the assessment from a workspace that exposes as many production client codebases as possible. The current checkout is not evidence that it contains the whole product.

Before assessing readiness:

1. Inspect the current repository and every workspace root available to the agent.
2. Infer supported client platforms from product documentation, CI, release configuration, workspace manifests, submodules, and references to sibling repositories.
3. Locate each production client codebase, including separate native iOS and Android repositories, app variants, and any web client relevant to staffing or proposed code sharing.
4. Record a platform inventory with the client, repository or path, evidence of product membership, and access status.

When iOS and Android are both supported, inspect both native codebases before recommending a path. If a codebase remains unavailable, mark its evidence `unknown`, state that the assessment covers only the accessible platforms, and lower confidence accordingly. Do not infer that a platform is unsupported merely because its project is absent from the current repository.

**Scope gate:** every supported production client is listed, and each codebase is accessible, explicitly unavailable, or confirmed not to exist.

## First Response Gate

When the scope gate has not passed, the first response must be exactly:

```markdown
**Question:** Where can I access the production codebase for each client platform this product supports, including iOS and Android if both exist?

**Why it matters:** A migration path based on only one platform can miss native dependencies, product behavior, and delivery constraints that change the decision.
```

After the scope gate passes, grill rather than survey when repository evidence is unavailable.

The rest: https://github.com/callstackincubator/agent-skills/blob/HEAD/skills/assess-react-native-migration/SKILL.md