maggy vs old-coder
Claude Code config pack + optional local harness: TDD-enforcing hooks, 67 skills, quality gates, persistent memory — plus a dashboard routing each task across 13 models by cost-aware blast score. — versus — Uncle Bob's strategy as a skill: the agent writes a SPEC you approve, then runs a gauntlet — tests, mutation, property-based, coverage, supply chain — and hands you an evidence report instead of code.
Both enforce test-first discipline on a coding agent. Maggy does it with Claude-Code-specific hooks and quality gates you install as config; old-coder does it as provider-agnostic Markdown whose output is a report you sign off. Enforcement versus evidence.
| maggy | old-coder | |
|---|---|---|
| Stars | 705 | 667 |
| Forks | 57 | 51 |
| Language | Python | Python |
| License | MIT | MIT |
| Last activity | 6 days ago | 6 days ago |
| Topics | coding, skills | skills, coding |
| Curated connections | 3 | 4 |
maggy — the curator's take
Two products in one repo — know which you're installing. Bootstrap is 30 seconds of files in ~/.claude and gives you the enforcement layer: stop-hooks that hold 'done' hostage to passing tests, quality gates, memory that survives compaction. Maggy is a bigger commitment — a FastAPI server, dashboard and 13-tier router sending ~80% of tasks to DeepSeek, a cost bet you should verify on your own work. 1100+ tests at ★704 is a real signal. Same warning as every kitchen-sink: 67 skills and hooks change how Claude behaves everywhere — read them before they run your sessions.
old-coder — the curator's take
The right skill when you've accepted you won't read the diff: you read two documents instead — a SPEC of concrete must and must-not examples before any code, and an EVIDENCE report with real numbers from one fresh run you can reproduce with a single command. Effort scales with risk, so a typo fix runs two checks while anything touching money, auth or concurrency runs mutation testing, property-based tests and hostile inputs. It's plain Markdown, so any instruction-following agent can use it. Read the honesty clause carefully: the gauntlet turns your spec into executable evidence, it cannot prove the spec is complete or authenticate its own checkers — the demo's own report caught an unsound mutation runner behind an earlier green state.