Skip to content

feat(init): install the clerk-expo setup skill for Expo projects#328

Open
manovotny wants to merge 2 commits into
mainfrom
manovotny/init-expo-setup-skill
Open

feat(init): install the clerk-expo setup skill for Expo projects#328
manovotny wants to merge 2 commits into
mainfrom
manovotny/init-expo-setup-skill

Conversation

@manovotny

Copy link
Copy Markdown

clerk init on Expo projects only installs clerk-expo-patterns. The expo entry in FRAMEWORK_SKILL_MAP (#86, April) predates the mobile/clerk-expo setup skill (clerk/skills@7f7b6ea, May), so the dedicated Expo setup skill never made it into the init flow.

This makes the framework skill map support multiple skills per framework and adds clerk-expo for Expo inits. Prompt summary becomes (clerk-cli + core + features + expo + expo-patterns).

If the exclusion was deliberate, feel free to close — we'll note the intent in docs instead. Surfaced while tightening CLI ↔ Skills cross-referencing in clerk-docs#3427 (DOCS-11816).

The expo entry in FRAMEWORK_SKILL_MAP (added in #86, 2026-04) predates the mobile/clerk-expo setup skill (added to clerk/skills in 2026-05), so Expo inits only got clerk-expo-patterns. The map now supports multiple skills per framework and Expo installs both.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@changeset-bot

changeset-bot Bot commented Jun 10, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 438581c

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
clerk Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@coderabbitai

coderabbitai Bot commented Jun 10, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: fc5116b6-a96c-4b5d-930a-9793237d16f2

📥 Commits

Reviewing files that changed from the base of the PR and between aa36552 and 438581c.

📒 Files selected for processing (1)
  • packages/cli-core/src/commands/init/skills.ts
🚧 Files skipped from review as they are similar to previous changes (1)
  • packages/cli-core/src/commands/init/skills.ts

📝 Walkthrough

Walkthrough

This PR refactors the skills system to support multiple framework-specific skills per framework. FRAMEWORK_SKILL_MAP now maps frameworks to arrays of skills; getFrameworkSkills() returns all mapped skills; resolveUpstreamSkills(), formatSkillsSummary(), and formatSkillsPromptMessage() operate on skill arrays; installSkills() and runSkillsAdd() use the array-based summaries. Tests cover Expo mapping to both "clerk-expo" and "clerk-expo-patterns", and release notes document the change.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately summarizes the main objective: installing the clerk-expo setup skill for Expo projects, which is the central change across all modified files.
Description check ✅ Passed The description is directly related to the changeset, clearly explaining the motivation (clerk-expo skill was never included in init flow) and the solution (support multiple skills per framework).
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@packages/cli-core/src/commands/init/skills.ts`:
- Around line 70-72: getFrameworkSkills currently returns the original array
from FRAMEWORK_SKILL_MAP which allows external mutation; change
getFrameworkSkills to return an immutable copy of the skills array (e.g., create
a new array via slice/spread or Object.freeze) when
FRAMEWORK_SKILL_MAP[frameworkDep] exists, while still returning an empty array
for unknown frameworkDep, so callers cannot modify the global
FRAMEWORK_SKILL_MAP contents.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: d7d6df06-9251-4bce-91ff-470e6da2f40b

📥 Commits

Reviewing files that changed from the base of the PR and between 4bd85a8 and aa36552.

📒 Files selected for processing (3)
  • .changeset/init-expo-setup-skill.md
  • packages/cli-core/src/commands/init/skills.test.ts
  • packages/cli-core/src/commands/init/skills.ts

Comment on lines 70 to 72
export function getFrameworkSkills(frameworkDep: string | undefined): string[] {
return (frameworkDep && FRAMEWORK_SKILL_MAP[frameworkDep]) || [];
}

@coderabbitai coderabbitai Bot Jun 10, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major | ⚡ Quick win

Return an immutable/copy value from getFrameworkSkills to prevent global map mutation.

Line 71 currently leaks the original array stored in FRAMEWORK_SKILL_MAP. Because this function is exported, any caller can mutate that array and silently change future skill resolution/install behavior.

Suggested fix
-export function getFrameworkSkills(frameworkDep: string | undefined): string[] {
-  return (frameworkDep && FRAMEWORK_SKILL_MAP[frameworkDep]) || [];
+export function getFrameworkSkills(frameworkDep: string | undefined): readonly string[] {
+  const skills = frameworkDep ? FRAMEWORK_SKILL_MAP[frameworkDep] : undefined;
+  return skills ? [...skills] : [];
 }
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@packages/cli-core/src/commands/init/skills.ts` around lines 70 - 72,
getFrameworkSkills currently returns the original array from FRAMEWORK_SKILL_MAP
which allows external mutation; change getFrameworkSkills to return an immutable
copy of the skills array (e.g., create a new array via slice/spread or
Object.freeze) when FRAMEWORK_SKILL_MAP[frameworkDep] exists, while still
returning an empty array for unknown frameworkDep, so callers cannot modify the
global FRAMEWORK_SKILL_MAP contents.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would suggest implementing this fix @manovotny

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems like the humans are having a chat. I'll hop back into my burrow for now. If you need me again, just tag @coderabbitai in a new comment, and I'll come hopping out!

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could if you like just modify the return type to be readonly which would enforce it on the type layer like:

Suggested change
export function getFrameworkSkills(frameworkDep: string | undefined): string[] {
return (frameworkDep && FRAMEWORK_SKILL_MAP[frameworkDep]) || [];
}
export function getFrameworkSkills(frameworkDep: string | undefined): ReadonlyArray<string> {
return (frameworkDep && FRAMEWORK_SKILL_MAP[frameworkDep]) || [];
}

@manovotny manovotny Jun 12, 2026

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Applied in 438581c, one level up from the return-type fix: FRAMEWORK_SKILL_MAP itself is now Record<string, readonly string[]>, so immutability is declared at the source and getFrameworkSkills inherits readonly string[] (matching the existing annotations on the format helpers).

Skipped the runtime copy — both callers only iterate, and with the readonly type any future mutation fails typecheck at the call site.

Review feedback on the FRAMEWORK_SKILL_MAP leak: type the map as
Record<string, readonly string[]> so immutability is declared at the
source and getFrameworkSkills inherits it, instead of copying at
runtime.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants