Code Review Plugins in Claude Code: Only One Is Built for the Job

Only one of these Claude Code plugins for code review is built for the job — a dedicated diff reviewer. See which bundles review and which two miss.

The n/a stars are not missing data. Four of these plugins come from a single source repo that hosts 21 plugins, so the repo's star count is not any one plugin's star count — treating it as such would be dishonest. Judge those four on what their skills do, not on a shared vanity number.

The dedicated reviewer and the kit that swallows it

mattpocock code-review: diff your branch, get parallel findings

This one does the narrow job well: it reviews the changes between HEAD and a fixed point for coding-style conformance and specification faithfulness, running parallel sub-agents that report side by side. Use it for a pre-PR self-review — point it at your feature branch and its base commit, and read both lanes before you ask a human. It differs from everything-claude-code in scope, not ambition: it is skills-only and does exactly one thing, where the larger kit ships four component types and many jobs. If review is the only task you want automated, start at its plugin page.

everything-claude-code: review as one lane in a 548-skill kit

ECC extends Claude Code with 548 skills, 185 commands, 134 agents, and 2 hooks, and its orchestration pipelines cover TDD, code review, and bug fixing among many other flows. Use it when you want a single install that handles review alongside testing, security, and deployment rather than a purpose-built reviewer. It is the only featured plugin that ships all four component types — including agents and hooks — where every other option here is skills-only; that breadth is the reason it draws 226,080 stars against 586 installs in the last seven days. If you are assembling a broad automation stack, its review lane fits naturally, and our guide to automating Claude Code workflows covers the surrounding setup. The kit lives at everything-claude-code.

The mattpocock suite: build first, then review

These four listings come from the same "skills for real engineers" collection, and they are designed to compose rather than compete. Review is one station on a line that runs from idea to commit.

mattpocock-skills: a composable set where review is one skill among many

This is the full collection: structured, AI-guided workflows for API design, refactoring, code review, TDD, prototyping, and documentation, each running a focused session that produces an artifact. Use it when you want review wired into the same toolbox as the rest of your engineering work instead of installed on its own. It differs from the standalone code-review listing by being the superset — same author, but the whole kit rather than the single reviewing skill. See the mattpocock-skills page for the skill list.

ask-matt: the router that sends you to the right flow

ask-matt does not review code itself; it guides you through a structured workflow — idea grilling, prototyping, PRD creation, implementation, and code review — by routing to the appropriate skill for your situation. Use it when you are not sure which of the mattpocock skills you need and want the plugin to pick. It complements the code-review skill directly: ask-matt decides when review is the next step, code-review does the reviewing. Start at the ask-matt page.

implement: TDD that ends at a review-and-commit gate

implement builds features from PRDs or issues using test-driven development, runs typechecks and tests at agreed seams, and then walks you through code review and commit. Use it when the work is scoped and you want the review to happen at the end of a disciplined build rather than as a separate pass. It pairs with the standalone reviewer: implement produces the diff and a first review, and you can hand the same branch to code-review for a focused second look. Its implement page has the details.

development-discipline: engineering guardrails, thinly documented

This listing ships skills only and carries no enrichedSummary in the snapshot, so treat it as thinly documented for review specifically. Its parent repository is a multi-harness marketplace whose skills lean toward engineering discipline and PR handling, which is why it lands in this category. Until it has a clearer per-plugin summary, prefer the mattpocock reviewer for actual diff review and use this for the broader guardrail habits it encodes. Its plugin page is the place to check whether that has changed.

Listed for code review, built to review something else

Two of the eight match the "review" keyword and nothing more. Knowing that up front saves an install you would uninstall an hour later.

ui-ux-pro-max: it reviews designs, not diffs

ui-ux-pro-max generates brand systems and accessible UI with design tokens, palettes, and shadcn/ui components, then reviews and optimizes visual quality with AI-driven art direction. The word "review" is real, but it means design critique, not code review — it never reads a diff. With 444 installs in the last seven days and 100,453 stars, it is a capable design tool in the wrong aisle here. If that is the job you actually have, our frontend design plugins roundup is the right list; the ui-ux-pro-max page covers its design work.

nature-skills: simulated peer review of papers, not PRs

nature-skills generates Nature-style scientific manuscripts, figures, and response letters and runs simulated peer review over research materials. That peer review is the keyword collision — it reviews academic writing, not source changes. With 133 installs in the last seven days and 20,042 stars, it is a real research tool, but its README is largely a recruitment notice, so it is thin on anything a code reviewer needs. Confirm the mismatch yourself on the nature-skills page.

Match the plugin to the review in front of you

The pick changes with the job, not the star count. For a focused diff review before you open a PR, install the mattpocock code-review skill — it is the only listing scoped to exactly that. If you are standing up a wider automation stack and want review to ride along with testing and deployment, everything-claude-code's pipeline is the pragmatic call. If you already work inside the mattpocock skills, let ask-matt route you and hand finished branches from implement into the reviewer. Skip ui-ux-pro-max and nature-skills for code review entirely; they belong to design and research work. Browse the full set on the plugins directory and try the dedicated reviewer on your next branch.