Ext Ops Panel
Open dashboard
Comparison

project-version-workflow vs gsd-plugin

project-version-workflow is a plugin bundle for AI coding tools published by ATreep. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). gsd-plugin is a plugin bundle for AI coding tools published by jnuyens. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-12. 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
Marketplaceproject-version-workflowgsd-plugin
Claude Code: claude-plugins-community Listed
Version: v260627-121434
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 4.5.5
Forks (GitHub): 12
Stars (GitHub): 90
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

project-version-workflow vs gsd-plugin
Factproject-version-workflowgsd-plugin
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)90 (better)
Forks (GitHub) (differs)0 (worse)12 (better)
Last releaseNot publishedNot published
Where it runsInstalls as a plugin bundleInstalls as a plugin bundle
TransportNot statedNot stated
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)Not published18
Parts of the bundle (differs)3126
Licence (differs)Not statedMIT
Repository (differs)github.com/atreep/project-version-workflowgithub.com/jnuyens/gsd-plugin
Changes in the last 7 days00
First seen2026-10-112026-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

project-version-workflow

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

Manage project's versions and iterations by a standard workflow on Claude Code. Generates a daily version tag (e.g. v260416), records the changes in update_log.txt along with the git username when available, commits them, and optionally pushes to remote. It checks for a clean repo, asks you to confirm the change summary, warns about sensitive files, and never force-pushes.

gsd-plugin

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

Get Shit Done Plugin - handles large codebase contexts - structured workflow plugin for Claude Code with 60+ slash commands, 21 agents, MCP server, hooks, and cross-session memory

How to run each

project-version-workflow

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

gsd-plugin

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: project-version-workflow · What it can do: gsd-plugin · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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