docs: prepare Claude Code plugin marketplace release notes#291
Open
Darkroom4364 wants to merge 1 commit intomainfrom
Open
docs: prepare Claude Code plugin marketplace release notes#291Darkroom4364 wants to merge 1 commit intomainfrom
Darkroom4364 wants to merge 1 commit intomainfrom
Conversation
📝 WalkthroughWalkthroughThis PR adds comprehensive marketplace documentation for the Claude Code plugin, including publishing guidelines, versioning discipline, submission copy templates, and local validation procedures across three documentation files. ChangesClaude Code Marketplace Documentation
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes Possibly related issues
Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 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 |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
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 `@docs/claude-code-integration.md`:
- Line 85: Update the ambiguous phrase in docs/claude-code-integration.md
("GitHub issue linked from the README/PR queue") to be explicit: either replace
it with the exact issue number (e.g., "GitHub issue `#285`"), remove the clause
and point readers to plugins/claude-code/MARKETPLACE.md only, or reword to "the
GitHub issue tracking the marketplace release" so it clearly references the
marketplace release issue; ensure the final sentence also retains the existing
MARKETPLACE.md reference.
🪄 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: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 4b68017c-c98a-4561-bc06-91a30b6dc6e1
📒 Files selected for processing (3)
docs/claude-code-integration.mdplugins/claude-code/MARKETPLACE.mdplugins/claude-code/README.md
| The plugin can be loaded locally today with `--plugin-dir`. Publishing to an official Claude plugin marketplace is an external release step: it requires final marketplace metadata, a release/versioning decision, local plugin smoke testing in Claude Code, and submission through Anthropic's plugin form. | ||
|
|
||
| Track the publishing checklist in the GitHub issue linked from the README/PR queue rather than treating it as part of the scanner binary release. | ||
| Track the publishing checklist in the GitHub issue linked from the README/PR queue rather than treating it as part of the scanner binary release. Marketplace copy, versioning notes, and local validation commands live in [`plugins/claude-code/MARKETPLACE.md`](../plugins/claude-code/MARKETPLACE.md). |
There was a problem hiding this comment.
Clarify the GitHub issue reference.
The phrase "GitHub issue linked from the README/PR queue" is vague. Consider either:
- Specifying the exact issue number (e.g., "issue
#285") - Removing the reference entirely since MARKETPLACE.md already contains the checklist
- Using clearer phrasing like "the GitHub issue tracking the marketplace release"
🤖 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 `@docs/claude-code-integration.md` at line 85, Update the ambiguous phrase in
docs/claude-code-integration.md ("GitHub issue linked from the README/PR queue")
to be explicit: either replace it with the exact issue number (e.g., "GitHub
issue `#285`"), remove the clause and point readers to
plugins/claude-code/MARKETPLACE.md only, or reword to "the GitHub issue tracking
the marketplace release" so it clearly references the marketplace release issue;
ensure the final sentence also retains the existing MARKETPLACE.md reference.
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
1 participant
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
Verification
git diff --checkprintf {tool_input.file_path=tests/fixtures/safe.py} | plugins/claude-code/scripts/scan-edited-file.shexits 0 and stays silent.printf {tool_input.file_path=tests/fixtures/vulnerable.py} | plugins/claude-code/scripts/scan-edited-file.shexits 2 and emits a 37-finding stderr summary.printf {tool_input.path=tests/fixtures/vulnerable.py} | plugins/claude-code/scripts/scan-edited-file.shexits 2.printf {tool_input.file_path=/does/not/exist.py} | plugins/claude-code/scripts/scan-edited-file.shexits 0 and stays silent.Notes
claude plugin validate plugins/claude-codewas attempted locally with Claude Code 2.1.119, but it did not return and was stopped. In-session Claude Code smoke testing remains tracked in #285.Closes part of #285.
Related: #290
Summary by CodeRabbit