Ext Ops Panel
Open dashboard
Comparison

auto-repo-setup vs GitWarren

auto-repo-setup is a plugin bundle for AI coding tools published by daymade. Marketplaces we read that list it: 1 (Community GitHub marketplaces). GitWarren is an MCP server published by klarluft. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-21. 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
Marketplaceauto-repo-setupGitWarren
Community marketplace daymade/claude-code-skills Listed
Version: 2.1.6
Forks (GitHub): 228
Stars (GitHub): 1 480
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.1
Downloads/month (npm): 630
Downloads/week (npm): 43
Forks (GitHub): 3
Stars (GitHub): 18
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

auto-repo-setup vs GitWarren
Factauto-repo-setupGitWarren
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)1 480 (better)18 (worse)
Forks (GitHub) (differs)228 (better)3 (worse)
Last release (differs)Not published2026-10-15
Where it runs (differs)Installs as a plugin bundleOn your machine (gitwarren)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 0
Parts of the bundle (differs)Not published4
Licence (differs)Not statedGPL-3.0-or-later
Repository (differs)github.com/daymade/claude-code-skillsgithub.com/klarluft/gitwarren-app
Changes in the last 7 days (differs)23
First seen (differs)2026-10-152026-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

auto-repo-setup

In its own words, on Community GitHub marketplaces:

Evidence-driven repository setup, repair, handoff, and safe Git workflow for Claude Code or Codex. Detects the actual stack from project instructions and manifests instead of assuming Python, ffmpeg, uv, or .env; preserves local work during sync/conflict handling; diagnoses repeated SessionStart output before editing config; and defaults routine startup behavior to AGENTS.md/CLAUDE.md or a normal Agent request. Lifecycle hooks are an explicit pre-prompt exception with guarded, idempotent Claude Code setup and runtime-specific Codex verification.

GitWarren

In its own words, on Official MCP Registry:

Code review on your own machine, for you and your coding agent. Nothing leaves your computer.

How to run each

auto-repo-setup As a Claude Code plugin

Claude Code
/plugin marketplace add daymade/claude-code-skills
/plugin install auto-repo-setup@daymade-skills

GitWarren As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio gitwarren -- npx -y gitwarren mcp --serve "<YOUR_SERVE>"

Requires: --serve

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

The marketplaces of auto-repo-setup publish no settings it asks for, so we do not compare settings.

What it can do: auto-repo-setup · What it can do: GitWarren · 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