feat(prepare): install Maizzle skill into .claude/skills on prepare - #1815
Merged
Conversation
Ship the bundled skill (add "skills" to package files) and copy skills/maizzle into <project>/.claude/skills/maizzle during prepare. Claude Code auto-discovers project-level .claude/skills/ but never scans node_modules, so shipping the skill alone is not discoverable. Running the copy from prepare (the postinstall step) makes it both discoverable and version-synced, refreshed on every install/upgrade. rm-then-copy prunes files removed upstream. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe package now publishes the ChangesBundled skill installation
Estimated code review effort: 2 (Simple) | ~10 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
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. Comment |
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.
What
Makes the bundled Maizzle skill available to Claude Code automatically after install.
skillsto the packagefilesarray soskills/maizzleships innode_modules/@maizzle/framework/.prepare(the starter'spostinstallstep), copyskills/maizzle→<project>/.claude/skills/maizzle.Why
Claude Code auto-discovers project-level
.claude/skills/(and~/.claude/skills/) but never scansnode_modules/. So shipping the skill in the package alone is necessary but not discoverable. Copying it into the project's.claude/skills/duringpreparemakes it:npm i/upgrade viapostinstall: maizzle prepare, instead of frozen at scaffold time in the starter.rm-then-cpprunes files removed upstream;cpSynccreates the.claude/skills/parents. Source is resolved from the package viaimport.meta.urland guarded withexistsSync, so it's a no-op when the skill isn't present.Test
npm pack --dry-runconfirmsskills/maizzle/**is in the tarball.🤖 Generated with Claude Code
Summary by CodeRabbit
New Features
Chores