SOC 직업 분류 기준
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/tomevault-io/tomes --skill upgrade-react-native명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
| name | upgrade-react-native |
| description | > Use when this capability is needed. |
Upgrade a React Native Community CLI project to a target version by fetching and applying the diff from the React Native Upgrade Helper.
[!Note] Expo users: For Expo projects or more complex upgrade scenarios, try:
/upgrade-react-native <targetVersion>
<targetVersion> — the React Native version to upgrade to (e.g. 0.79.0).Follow every step below in order. Do not skip steps.
Read the project's root package.json and extract the react-native version
from dependencies (or devDependencies). Strip any semver range prefix
(^, ~, >=, etc.) to get the exact current version string.
If the current version cannot be determined, stop and ask the user.
0.79.0).https://raw.githubusercontent.com/react-native-community/rn-diff-purge/master/RELEASES
Fetch the unified diff between the two versions:
https://raw.githubusercontent.com/react-native-community/rn-diff-purge/diffs/diffs/<currentVersion>..<targetVersion>.diff
For example, to upgrade from 0.73.0 to 0.74.0:
https://raw.githubusercontent.com/react-native-community/rn-diff-purge/diffs/diffs/0.73.0..0.74.0.diff
If the diff cannot be fetched (404), it may be because exact patch versions are
not available. Try the nearest minor versions (e.g. 0.73.0 instead of
0.73.2). Report what you tried and ask the user if needed.
The diff uses the template project name RnDiffApp. Map every path in the diff
to the actual project:
| Diff path prefix | Actual project path |
|---|---|
RnDiffApp/ | Project root (./) |
Additionally, replace occurrences of the template identifiers with the project's actual names:
| Template value | Replace with |
|---|---|
RnDiffApp | The project's app name (from app.json → name, or the name field in package.json) |
rndiffapp | Lowercase version of the project's app name |
com.rndiffapp | The project's Android package name (from android/app/build.gradle or android/app/src/main/AndroidManifest.xml) |
Before making any edits, review the entire diff and categorize changes:
- lines. These can be applied as-is.Present this plan to the user before proceeding. Group changes by area:
package.json, metro.config.js, .eslintrc.js, etc.)ios/ directory)android/ directory)Apply the changes following the plan from step 5:
+ lines.Important considerations:
package.json, update the react-native version and any
related dependencies mentioned in the diff (e.g. react, @react-native/*
packages, Gradle versions, CocoaPods versions).npm install / yarn install / pod install automatically.
Inform the user these steps are needed after the upgrade.Scan the project's dependencies and devDependencies in package.json for
third-party React Native libraries that contain native code (i.e. they have
an ios/ or android/ directory, or are known native modules). Common examples
include react-native-screens, react-native-reanimated,
react-native-gesture-handler, @react-native-async-storage/async-storage,
react-native-svg, react-native-safe-area-context, etc.
For each candidate dependency:
Present all proposed dependency bumps alongside the diff-based changes in step 5 (grouped under a Third-party native dependencies section). For each:
Apply these version bumps to package.json as part of step 6.
After applying all changes, present the user with a checklist:
npm install or yarn install to update JS dependenciescd ios && bundle exec pod install (or npx pod-install) to update
native iOS dependenciescd android && ./gradlew cleancd ios && xcodebuild cleanConsult these for version-specific migration guidance:
Source: callstack/repack — distributed by TomeVault.
> Use when this capability is needed.
Use when writing kernel, account, or note MASM code that reads from or writes to the advice provider (advice stack / advice map) — validate advice data.
Use when writing a Rust test that exercises a failure path or a MASM test that expects a `panic` / `assert` — assert on the specific expected error variant or error code.