commit-craft vs GitHub
commit-craft is a plugin bundle for AI coding tools published by Alireza Rezvani. Marketplaces we read that list it: 1 (Community GitHub marketplaces). GitHub is an MCP server published by github. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-11-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
| Marketplace | ||
|---|---|---|
| Community marketplace alirezarezvani/claude-skills | Listed Version: 2.14.6 Forks (GitHub): 4 120 Stars (GitHub): 29 704 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.1.0 Forks (GitHub): 5 333 Stars (GitHub): 34 391 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:f6056fc10bff Forks (GitHub): 5 333 Stars (GitHub): 34 391 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 | commit-craft | GitHub |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 29 704 (worse) | 34 391 (better) |
| Forks (GitHub) (differs) | 4 120 (worse) | 5 333 (better) |
| Last release (differs) | 2026-11-03 (worse) | 2026-11-04 (better) |
| Where it runs (differs) | Installs as a plugin bundle | Remote server or your machine |
| Transport (differs) | Not stated | Streamable HTTP, stdio |
| Tools it declares (differs) | Not published | 40 |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Parts of the bundle (differs) | 4 | Not a bundle |
| Licence | MIT | MIT |
| Repository (differs) | github.com/alirezarezvani/claude-skills | github.com/github/github-mcp-server |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-31 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 2 h ago, requires authentication |
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
commit-craft
Turn a tangled working tree into a clean, reviewable commit series. Three deterministic stdlib scripts over git: a series planner that groups changes into commits in build-safe order (manifest with lockfile, pure moves, formatting, each module's change with its tests, docs, CI), holds back .env and key files, and flags mixed formatting and moves whose callers would break; a secret gate that scans staged or pushed lines for provider tokens, high-entropy secrets, sensitive files and conflict markers and blocks before the commit exists, with redacted output and reasoned waivers; and a message linter that blocks vague subjects, missing why on large changes and pending fixup commits, matching the repo's own convention. Ships pre-commit, commit-msg and pre-push hooks, cs-commit-craft agent, /cs-commit-craft and /cs-commit-check commands and 3 cited references.
GitHub
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
How to run each
commit-craft As a Claude Code plugin
/plugin marketplace add alirezarezvani/claude-skills
/plugin install commit-craft@claude-code-skills
GitHub As a remote MCP server
claude mcp add --transport http github-mcp-server https://api.githubcopilot.com/mcp/ --header "Authorization: Bearer <YOUR_TOKEN>"
Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only GitHub has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of commit-craft publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of commit-craft publish no settings it asks for, so we do not compare settings.
What it can do: commit-craft · What it can do: GitHub · 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. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.