Claude Code code-review plugin (a plugin command, not a Skill)

When to use

• You want an automated review of a pull request with meaningful changes; the README lists this as a use case.[1]
• The repo has CLAUDE.md files and you want the review to check against them; the README says this gives better results.[1]

When not to use

• Closed or draft PRs, or PRs that need no review (for example automated or obviously correct trivial changes): the command file says it stops. The README also says already-reviewed PRs are skipped, but the command file's actual condition is that Claude has already commented on the PR.[1][5]
• Urgent hotfixes that must merge immediately; the README lists this as not suitable.[1]

What it does

The README says /code-review launches 4 agents in parallel, scores each issue 0-100 for confidence, and filters out anything below 80. Output goes to the terminal by default; the --comment flag posts it as a PR comment. The command file at the same SHA (commands/code-review.md) describes a different flow, shown in the table below; the agent roles and scoring here are the README's description and are not treated as the confirmed implementation.[1][5]

[1]

• The README says it first checks whether a review is needed: closed, draft, trivial or already-reviewed PRs are skipped (the command file's actual conditions are in the table below)
• The README says it summarizes the PR changes and gathers the relevant CLAUDE.md files
• The README says it filters pre-existing issues, pedantic nitpicks and issues a linter would catch (the command file's exclusion list is similar)

[1][5]

[1][5]

Invocation and install

The entry point is the slash command /code-review with an optional --comment flag. The plugin's own README Installation section only says the plugin is included in the Claude Code repository and the command is available automatically, with no install command. The repository root README at the same SHA says plugins install with /plugin install {plugin-name}@claude-plugins-official or can be browsed under /plugin > Discover. Substituting the plugin.json name (code-review) is an inference; the official text does not print that exact command. The two statements (automatic vs install) disagree, and Claude Code also ships a bundled skill with the same /code-review name (with different arguments), so which one runs is to be confirmed.[1][6][2][7][4]

/code-review
/code-review --comment

[1]

Version conflict: plugin.json (at the pinned SHA) names the plugin code-review at version 1.0.1, while the README at the same SHA ends with a Version section of 1.0.0. Which one applies is to be confirmed; this page does not guess.[2][1]

Requirements and license

[1][3]

The README's Troubleshooting section says that when gh fails, install it and run gh auth login. The command file's allowed-tools lists Bash(gh issue view/search/issue list/pr comment/pr diff/pr view/pr list:*) and mcp__github_inline_comment__create_inline_comment (posting inline comments needs that MCP tool). Account details and cost are not stated officially.[1][5]