Ext Ops Panel
Open dashboard
Comparison

claude-human-review vs ai.openhelm/dev-changes

claude-human-review is a plugin bundle for AI coding tools published by IrtezaAsadRizvi. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-community, Community GitHub marketplaces). ai.openhelm/dev-changes is an MCP server published by openhelm.ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceclaude-human-reviewai.openhelm/dev-changes
Claude Code: claude-plugins-community Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 15
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.0
No figure published
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

claude-human-review vs ai.openhelm/dev-changes
Factclaude-human-reviewai.openhelm/dev-changes
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)15No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (mcp.openhelm.ai/dev/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)3Not published
Parts of the bundle (differs)4Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/irtezaasadrizvi/claude-human-reviewNot stated
Changes in the last 7 days (differs)20
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 4 days ago

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

claude-human-review

In its own words, on Claude Code: claude-plugins-community:

claude-human-review adds a human approval gate at the end of every Claude Code turn that edits files. When Claude tries to stop, the plugin pauses it and has Claude do two things before the turn ends. First, drop a one-line doc comment on any class, function, or non-obvious config block it created or materially changed, using the right style per language (JSDoc for TS/JS, docstrings for Python, // for Go, and so on). Second, write a short plain-English review of what changed and why, flagging risks the diff alone won't show.\n You reply with 1 (Approve) to keep the changes or 2 (Undo) to roll them back. Undo is deterministic: filesystem snapshots are taken before each edit, so it works in git repos, non-repos, and folders full of untracked files. State lives on disk, so it survives Claude's context compaction on long sessions.\n The review is tuned to stay around 60 to 120 words per turn and skips sections when they would be filler, so the extra output-token cost is small. Inline comments are capped to one li

ai.openhelm/dev-changes

In its own words, on Official MCP Registry:

Turn described changes into reviewed pull requests: propose, triage, review, dependency audits.

How to run each

claude-human-review As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install claude-human-review@claude-community

ai.openhelm/dev-changes As a remote MCP server

Claude Code
claude mcp add --transport http dev-changes https://mcp.openhelm.ai/dev/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only ai.openhelm/dev-changes has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: claude-human-review · What it can do: ai.openhelm/dev-changes · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built