prebuild-native

Validate Expo native configurations before EAS builds using git worktrees and PNPM.

2|1|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/passionseed/ps_app --skill prebuild-native
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prebuild-native
Source: https://github.com/passionseed/ps_app/tree/main/.claude/skills/prebuild-native
Command: npx skills add https://github.com/passionseed/ps_app --skill prebuild-native

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fast native pre-build gate for Expo apps that catches native/configuration issues before expensive EAS previews or production builds. Use it when you want to prebuild, smoke test iOS or Android, run fast local native checks, validate native compilation, or prepare for EAS builds.

Core Features & Use Cases

  • Deterministic prebuild gate that quickly validates native configuration and reduces risk of failing builds.
  • Supports gating for iOS and Android native projects, with guidance to isolate issues and retry.
  • Prepares for EAS builds by validating output artifacts without modifying main repository.

Quick Start

From the repo root, run the prebuild-native gate to quickly validate native configurations before proceeding with EAS builds.

Frequently Asked Questions about prebuild-native

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate native configuration before expensive Expo EAS builds?

To validate native configuration before Expo EAS builds, use a deterministic prebuild gate that runs local native checks leveraging git worktrees, PNPM, and Expo Doctor to catch configuration failures early.

Can I smoke test iOS and Android native projects locally without modifying the main repository?

You can smoke test iOS and Android native projects locally by running a prebuild gate that uses isolated git worktrees, validating native compilation and output artifacts without modifying your main repository.

What's the best way to catch native compilation failures before running Expo builds?

The best way to catch native compilation failures before Expo builds is to run a fast local prebuild gate that performs controlled native generation steps and isolates issues with a clear reporting format.

Does this prebuild workflow require PNPM and git worktrees?

Yes, the deterministic prebuild workflow requires PNPM and git worktrees to enforce isolated native generation steps, ensuring native compilation is validated quickly without risking your main repository state.

Why do my EAS production builds keep failing on native configuration issues?

EAS production builds often fail on native configuration issues because local validation was skipped; running a prebuild gate with Expo Doctor catches these native config failures before expensive cloud builds.

When do I need to run a native prebuild gate for my Expo app?

You need to run a native prebuild gate when you want to prebuild quickly, smoke test iOS or Android, run local native checks, validate native compilation, or prepare for EAS previews and production builds.