chore(peek): rename the Claude Code plugin to peekdev (community-catalog de-confliction)#141
chore(peek): rename the Claude Code plugin to peekdev (community-catalog de-confliction)#141harry-harish wants to merge 1 commit into
peekdev (community-catalog de-confliction)#141Conversation
…talog de-confliction) The bare name `peek` is already held in Anthropic's `claude-community` marketplace by an unrelated project (gopeek.ai), and catalog entry names are globally unique — so our submission can only be listed under a distinct name. Rename the plugin `peek` -> `peekdev` in `plugins/peek/.claude-plugin/plugin.json` and the repo marketplace entry (own install becomes `peekdev@peek`; community target `peekdev@claude-community`; skill namespace `/peekdev:peek`). Update the drift guard (`plugin-checks.mjs`) + its tests and the three install-command docs (plugin README, @peekdev/mcp README, the Claude Code setup recipe) to match. Unchanged: the directory `plugins/peek/` (so the git-subdir submission path holds), the MCP server name `peek`, and the tool namespace `mcp__peek__*`. The bundled skill is untouched (still byte-identical to the canonical copy). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: harry-harish <22562634+harry-harish@users.noreply.github.com>
|
Warning Review limit reached
Next review available in: 3 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (8)
✨ 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 |
Why
The peek plugin's Console submission shows Published, but it's absent from the
anthropics/claude-plugins-communitycatalog — because the bare namepeekisalready held by an unrelated plugin (gopeek.ai /
Project-White-Rabbit/peek-claude-plugin,present since the catalog's first sync 2026-03-23). Catalog entry names are globally
unique (2,199 plugins / 2,199 distinct names) and the entry name is the install key,
so our plugin can only be listed under a distinct name.
This renames the plugin's install identity to
peekdev(matches our npm scope@peekdev) so it can list aspeekdev@claude-community.What changed
plugins/peek/.claude-plugin/plugin.json—name:peek→peekdev.claude-plugin/marketplace.json— plugin entryname→peekdevpackages/docs-shared/scripts/lib/plugin-checks.mjs(+ tests) — the drift guardhardcoded
"peek"; now expectspeekdev/plugin install peekdev@peek(plugin README,@peekdev/mcpREADME, the Claude Code setup recipe)
@peekdev/mcp(its shipped README changed)User-facing ripples (intended): own install
peek@peek→peekdev@peek;skill invocation
/peek:peek→/peekdev:peek.Deliberately unchanged: the directory
plugins/peek/(keeps the git-subdirsubmission
pathstable), the MCP server namepeek, and the tool namespacemcp__peek__*. The bundled skill is untouched (still byte-identical to the canonicalpackages/peek-cli/skills/peek-skill.md).Verification
pnpm verify:plugin→ OK ·claude plugin validate(plugin + marketplace) → ✔node --testdocs-shared → 14/14 (23/23 full docs-shared) ·pnpm lint(528 files) → cleanpeekdevis free in the live community catalog; no straypeek@peekremainsNote: after merge, the Console submission should be pointed at the
peekdevname (aseparate, out-of-band step).
🤖 Generated with Claude Code