Two first-party /code-review commands (bundled skill + official plugin) collide with contradictory docs #69232

Summary

There appear to be two different first-party /code-review implementations that share the same command name and ship with overlapping, partly contradictory documentation. As a user it's genuinely hard to tell which one you're invoking, how they relate, or whether you need to install anything.

The two implementations

1. Bundled skill — /code-review, documented in the commands reference (tagged [Skill]). Reviews the current diff with effort tiers (low…ultra), plus --fix, --comment, and an ultra cloud review.
2. code-review@claude-plugins-official plugin — also first-party (author listed as Boris Cherny, Anthropic). Its commands/code-review.md reviews a pull request via the gh CLI using parallel agents and a 0–100 confidence filter, then posts a PR comment.

With the plugin enabled, the skills list shows both /code-review (bundled skill) and /code-review:code-review (plugin command).

What's confusing

• The plugin's README.md, under an Installation heading, says: "This plugin is included in the Claude Code repository. The command is automatically available when using Claude Code." That simultaneously implies it's the built-in command and that you install it — and it never mentions that a separate bundled /code-review skill now exists with a richer feature set (effort tiers, --fix, ultra). It reads as if installing the plugin is how you get /code-review, when /code-review already works without it.
• The official marketplace mixes plugins that are bundled-by-default, install-required, first-party, and community-authored, with little signal distinguishing them. (For example, the github plugin is just the same https://api.githubcopilot.com/mcp/ MCP server a user may already be declaring themselves, with env-var auth instead — easy to install redundantly.)
• Net effect: it's unclear whether you need to install anything, which /code-review you're actually running, and how the bundled skill and the plugin relate.

Suggestions (any subset would help)

1. In the plugin's README, note that a bundled /code-review skill exists, explain how the two differ, recommend which to use, and fix the "automatically available" line that reads as contradictory under an Installation heading.
2. If the bundled skill supersedes the plugin, consider deprecating/retiring the plugin or renaming its command so it doesn't collide on /code-review.
3. In the marketplace UI/docs, clearly distinguish bundled/default vs install-required, and first-party vs community plugins.

Thanks for all the work on Claude Code — to be clear this is a docs/UX paper cut, not a functional bug. Happy to add more detail or screenshots if useful.

Environment

• Claude Code (CLI), macOS
• claude-plugins-official marketplace