git-bisect-pr-review vs Infrawise
git-bisect-pr-review is a plugin bundle for AI coding tools published by Pierre-louis242. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Infrawise is an MCP server published by Sidd27. Marketplaces we read that list it: 3 (Official MCP Registry, npm registry (MCP servers), Community GitHub marketplaces). As of our marketplace pass on 2026-10-28. 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
| Marketplace |  git-bisect-pr-review |  Infrawise |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 1.2.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 Downloads/month (npm): 1 026 Downloads/week (npm): 100 Forks (GitHub): 5 Stars (GitHub): 22 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 1.0.0 Downloads/month (npm): 1 026 Downloads/week (npm): 100 Forks (GitHub): 5 Stars (GitHub): 22 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
| Fact | git-bisect-pr-review | Infrawise |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 3 (better) |
| Stars (GitHub) (differs) | 0 (worse) | 22 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 5 (better) |
| Last release (differs) | Not published | 2026-10-21 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (infrawise) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 2 | 1 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/pierre-louis242/git-bisect-pr-review | github.com/sidd27/infrawise |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
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
git-bisect-pr-review
Two skills in one plugin: (1) Automated git bisect for regression hunting — establishes boundaries, runs `git bisect run` with reproduction commands, analyzes the culprit commit, and suggests fixes. (2) Structured PR review — loads PR context via `gh` CLI, reviews across five dimensions (code quality, test coverage, security, performance, CI status), posts inline and general comments, handles approvals, and merges with the repo's preferred strategy. Includes safety rails: never merges without user confirmation, never force-pushes to protected branches. Requires `gh` CLI.
Infrawise
Live AWS, database & Kafka infrastructure context for AI coding assistants via MCP.
How to run each
git-bisect-pr-review As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install git-bisect-pr-review@claude-communityInfrawise As a local MCP server: npm package
claude mcp add --transport stdio infrawise -- npx -y infrawiseCommands built only from what the marketplaces declare; the full set for every client is on each card.
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: git-bisect-pr-review · What it can do: Infrawise · 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 the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.