← AnsightCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to Ansight
Snapshot Sep 30, 2026 · 23:15 UTC · version 0.1.0
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"name": "ansight-install-react-native",
"description": "Install @ansight/react-native in React Native or Expo development builds with automatic simulator or emulator registration and one-shot CLI QR enrollment for physical devices. Add and link the package, initialize native defaults, expose enrollFromQrCode from a developer-only surface, keep remote tools development-only, verify JavaScript and native builds, and inspect the app through the Ansight CLI.",
"included_files": [],
"skill_md_contents": "---\nname: ansight-install-react-native\ndescription: Install @ansight/react-native in React Native or Expo development builds with automatic simulator or emulator registration and one-shot CLI QR enrollment for physical devices. Add and link the package, initialize native defaults, expose enrollFromQrCode from a developer-only surface, keep remote tools development-only, verify JavaScript and native builds, and inspect the app through the Ansight CLI.\n---\n\n## OpenAI plugin integration\n\nRun Ansight CLI commands using the execution tools in ChatGPT Work or Codex on the machine that owns the resident host. If this environment cannot execute commands or reach that host, explain the missing prerequisite and do not claim a live inspection succeeded. A remote workspace or cloud agent does not automatically have access to the developer’s local host. Resolve relative helper paths from this skill’s directory. When this workflow references another bundled skill, read its local SKILL.md completely before following it.\n\nUse these bundled files for the canonical skill URLs referenced below; keep public URLs when writing documentation for the user’s app:\n\n- https://www.ansight.ai/skills/agents/ansight-app-inspection.md → [ansight-app-inspection](../ansight-app-inspection/SKILL.md)\n- https://www.ansight.ai/skills/react-native/ansight-app-inspection-react-native.md → [ansight-app-inspection-react-native](../ansight-app-inspection-react-native/SKILL.md)\n\n\n# Ansight React Native Install Skill\n\nUse this skill for React Native apps, including Expo development builds, with native Android and iOS projects. Expo Go cannot load the native Ansight bridge.\n\n## Workflow\n\n1. Identify the package manager, bootstrap path, native projects, app ids,\n debug guard, and existing developer menu.\n2. Install and link:\n\n```shell\nnpm install @ansight/react-native\nnpx pod-install\n```\n\n3. Initialize once from app bootstrap:\n\n```ts\nif (__DEV__) {\n await Ansight.initializeAndActivate({\n useNativeAllInOneDefaults: true,\n toolGuard: \"readOnly\",\n });\n}\n```\n\n4. Add a developer-only scanner action:\n\n```ts\nawait Ansight.enrollFromQrCode({\n clientName: \"React Native App\",\n});\n```\n\n5. `scanPairingQrCode(...)` is an API alias. If the app already owns a scanner,\n pass its result to `connect(...)`.\n6. Keep native and React inspection tools behind `__DEV__` or the app's\n equivalent local-development guard. Disable tools outside that guard.\n7. Android requires no app camera permission for the SDK scanner. On iOS, add\n `NSCameraUsageDescription` and `NSLocalNetworkUsageDescription`. Add no ATS\n exception or unrelated permissions.\n8. Create or update `ansight-readme.md` with the scanner location, selected tool\n profile, build checks, and CLI enrollment commands. Do not include an enrollment payload.\n9. Run JavaScript checks and practical Android/iOS debug builds.\n10. Start or reuse the resident CLI host. A simulator or emulator registers\n automatically. For a physical device, issue one generic host QR and scan it\n from the developer-only surface:\n\n```sh\nansight host run\nansight pairing issue --qr\nansight session list --connected --app-id <app-id> --json\nansight app tools <session-id> --detail summary --include-unavailable --max-results 50 --json\n```\n\n Do not require `ansight app register` before the first connection. After\n the SDK supplies its real App ID, optionally link the discovered app to the\n repository with `ansight app register <app-id> --codebase <repository-path>`.\n\n## Enrollment Behavior\n\nSimulator and emulator builds register automatically through native loopback.\nThe first physical-device scan registers the native app installation. Its random installation\nid and enrollment state remain in app-private native storage, so later\ndeveloper launches reconnect automatically.\n\n## Recommended Inspection Skills\n\nUse the main router to select the core inspection workflow. Add the React\nNative companion only when React, shadow-tree, or native-rendering semantics\nare material:\n\n```text\nhttps://www.ansight.ai/skills/agents/ansight-app-inspection.md\nhttps://www.ansight.ai/skills/react-native/ansight-app-inspection-react-native.md\n```\n"
}SHA-256: 45c2d77d25184322e72ef833292ed821c9d6de9b8d945ea01fc03b9f1f3ff296