feat: add expo-when-to-rebuild skill#77
Open
zvadaadam wants to merge 2 commits into
Open
Conversation
Teaches the Expo core development loop: whether a change needs a new native build (the JS vs. native boundary), local vs. EAS Build, and CNG / `prebuild --clean`. Includes a Mermaid decision diagram, a quick decision table, and the prebuild .gitignore/--clean gotcha. Indexed in the plugin README next to its sibling expo-dev-client. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Expo-docs fact-check pass: - Remove "routing" as an app-config property (it's Expo Router / JS). - Reframe the no-rebuild app-config row around runtime values read via expo-constants (e.g. extra), per the configuration docs. - Correct .gitignore guidance: android/ios are git-ignored by default in a CNG project, not something you add. - Soften "most npm libraries" to "JS-only libraries" (many RN libs are native). - Deliver on the description's Expo Go vs. development build promise, and add an autolinking note for why native changes need a rebuild. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
sunilgentyala
approved these changes
Jun 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a new skill,
expo-when-to-rebuild, for the front half of Expo's core development loop — the decision developers hit constantly: "I changed something, do I need a new native build?" The existing skills are all task "spokes"; none owned this mental model. It stays distinct fromexpo-dev-client(which covers how to build & distribute) — this covers whether & which.What's included
expo-dev-client).prebuild --clean/.gitignoregotcha called out in the docs.expo-dev-client,expo-module,upgrading-expo,expo-cicd-workflows.Changes
plugins/expo/skills/expo-when-to-rebuild/SKILL.mdplugins/expo/README.mdValidated with
claude plugin validate ./plugins/expo✔.🤖 Generated with Claude Code