zhukang/manus-skills
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
e343dcb8f2
manus-skills/.kortix/opencode/skills/coding/upgrading-react-native/references/upgrade-verification.md
zhukang 1c7abd81d1 All 310 Manus skill-hub community skills as a Kortix marketplace registry 
- 310 registry:skill items, 1528 files, 7 categories (hub tags)
- registry.json generated by @kortix/registry buildRegistry
- nested SKILL.md in sn-da-* renamed SUBSKILL.md (no phantom skills)
- provenance + licenses: SOURCES.md
2026-09-15 13:37:20 +08:00

2.4 KiB
Raw Blame History

title impact tags
Upgrade Verification HIGH verification, regression, android, ios, navigation

Skill: Upgrade Verification

Manual and agent-assisted validation checklist after React Native and/or Expo upgrades.

Scope

  • Focus on behavior and UX regressions that static diffs cannot prove.
  • Keep checks small, repeatable, and tied to critical user flows.

Agent-Assisted Checks

Use agent-device for runnable app verification. If it is missing and device verification is needed, install it through the environment's approved/trusted path or ask the user to install or enable it.

  1. If the agent environment exposes an agent-device skill, read it before planning exact commands.
  2. If the agent-device CLI is available, follow its agent-device help workflow guidance.
  3. Open or install the upgraded app, drive each critical scenario, and verify with UI snapshots.
  4. Capture screenshots, logs, and pass/fail evidence for changed flows.
  5. Fall back to human validation for credentials, physical-device-only hardware, or profiler surfaces the agent cannot inspect.

Behavior Checks (Required)

  1. App launch and core journeys work on both iOS and Android.
  2. Navigation behavior is correct (forward/back stack, params, deep links, modal flows).
  3. Android edge-to-edge is visually correct (status bar, nav bar, safe area insets, keyboard overlays).
  4. Permissions and device APIs work (camera, location, notifications, file/media access).
  5. Background/restore paths work (app resume, push open, interrupted flows).

Build and Test Gates

  1. Run unit/integration tests and fix all upgrade-related failures.
  2. If target_version >= 0.81 and tests fail due to missing modules, add proper mocks.
  3. Build installable artifacts for both platforms.
  4. For Expo apps, run npx expo-doctor from expo-sdk-upgrade.md.

Evidence to Capture

  • Screen recordings/screenshots for changed flows.
  • List of verified scenarios and pass/fail status.
  • Follow-up fixes for any observed regressions.

Related Skills