Ext Ops Panel
Open dashboard
Comparison

rebase-stack vs GenPark Git Semantic Cherry-Pick Conflict Resolver

rebase-stack is a plugin bundle for AI coding tools published by ryanb. Marketplaces we read that list it: 1 (Community GitHub marketplaces). GenPark Git Semantic Cherry-Pick Conflict Resolver is an MCP server published by alphaparkinc. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-11. 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
Marketplacerebase-stackGenPark Git Semantic Cherry-Pick Conflict Resolver
Community marketplace ryanb/dotfiles Listed
Version: not stated
Forks (GitHub): 765
Stars (GitHub): 2 399
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.1
Forks (GitHub): 0 (last published figure)
Stars (GitHub): 7 (last published figure)
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

rebase-stack vs GenPark Git Semantic Cherry-Pick Conflict Resolver
Factrebase-stackGenPark Git Semantic Cherry-Pick Conflict Resolver
Marketplaces that list it11
Stars (GitHub) (differs)2 3997 (last published figure)
Forks (GitHub) (differs)7650 (last published figure)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (https://github.com/Alpha-Park/genpark-git-semantic-cherry-pick-conflict-resolver-skill/releases/download/v1.0.1/genpark-git-semantic-cherry-pick-conflict-resolver-skill.mcpb)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/ryanb/dotfilesgithub.com/alphaparkinc/genpark-git-semantic-cherry-pick-conflict-resolver-skill
Changes in the last 7 days00
First seen (differs)2026-11-042026-10-19

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

rebase-stack

In its own words, on Community GitHub marketplaces:

Rebase or reorder a stack of dependent PR branches across worktrees.

GenPark Git Semantic Cherry-Pick Conflict Resolver

In its own words, on Official MCP Registry:

Three-way AST hunk alignment and non-overlapping block conflict resolution for Git cherry-picks

How to run each

rebase-stack As a Claude Code plugin

Claude Code
/plugin marketplace add ryanb/dotfiles
/plugin install rebase-stack@ryanb-dotfiles

GenPark Git Semantic Cherry-Pick Conflict Resolver

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Commands 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: rebase-stack · What it can do: GenPark Git Semantic Cherry-Pick Conflict Resolver · Compare two other plugins

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