docs: clarify plugin metadata terminology#75
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (4)
📝 WalkthroughWalkthroughFour metadata/manifest files have their ChangesDescription Text Update
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 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 |
Summary
Test Plan / Validation
git diff --checkpython3JSON/TOML parse forpackage.json,plugin/.claude-plugin/plugin.json,.claude-plugin/marketplace.json, andplugin/pyproject.tomlnpm pack --dry-run --jsonMarketing rationale
This is a low-risk metadata-only change that reinforces the core public pitch: claude-smart turns corrections and working patterns into durable learning artifacts that future Claude Code and Codex sessions can reuse.
Summary by CodeRabbit