auto-repo-setup vs io.github.sgroy10/speclock
auto-repo-setup is a plugin bundle for AI coding tools published by daymade. Marketplaces we read that list it: 1 (Community GitHub marketplaces). io.github.sgroy10/speclock is an MCP server published by sgroy10. 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
| Marketplace | ||
|---|---|---|
| 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: 5.5.3 Downloads/month (npm): 863 Downloads/week (npm): 186 Forks (GitHub): 6 Stars (GitHub): 25 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 | auto-repo-setup | io.github.sgroy10/speclock |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 1 480 (better) | 25 (worse) |
| Forks (GitHub) (differs) | 228 (better) | 6 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (speclock) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | Not published | 1 |
| Parts of the bundle (differs) | Not published | 3 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/daymade/claude-code-skills | github.com/sgroy10/speclock |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-15 | 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
auto-repo-setup
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.
io.github.sgroy10/speclock
AI Constraint Engine — enforces CLAUDE.md and .cursorrules as laws. 51 MCP tools.
How to run each
auto-repo-setup As a Claude Code plugin
/plugin marketplace add daymade/claude-code-skills
/plugin install auto-repo-setup@daymade-skills
io.github.sgroy10/speclock As a local MCP server: npm package
claude mcp add --transport stdio speclock -- npx -y speclock
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: auto-repo-setup · What it can do: io.github.sgroy10/speclock · 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.