AmazingAng/

old-coder

GitHub

An old coder's strategy for the agent era: don't read the code — make it run the gauntlet. Evidence-first development skill for coding agents, inspired by Uncle Bob.

294stars

+1727 days

20forks

1issues

MITlicense

2026since

Star historydaily snapshots by VibeCrowd

Alternatives & relatedmatched by topic overlap

Graphify-Labs/

graphify

▲ 4.6k/wk

Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.

102k9.9kPython

zhayujie/

CowAgent

▲ 135/wk

Open-source super AI assistant & Agent Harness. Plans tasks, runs tools and skills, self-evolves with memory and knowledge. Multi-model, multi-channel. Lightweight, extensible, one-line install. (formerly chatgpt-on-wechat)

46k10kPython

ruvnet/

ruflo

▲ 629/wk

🌊 The original agent meta-harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, RAG integration, and native Claude Code / Codex / Hermes and many more Integrated

67k8.0kTypeScript

farion1231/

cc-switch

▲ 2.3k/wk

A cross-platform desktop All-in-One assistant for Claude Code, Codex, OpenCode, OpenClaw, Grok Build & Hermes Agent. Only official website: ccswitch.io

124k8.4kRust

addyosmani/

agent-skills

Production-grade engineering skills for AI coding agents.

82k8.8kJavaScriptgiant

Leonxlnx/

taste-skill

Taste-Skill - gives your AI good taste. stops the AI from generating boring, generic slop

72k4.9kJavaScriptgiant

Compareold-coder vs graphify old-coder vs CowAgent old-coder vs ruflo

Agent skills inside · 1

All skills →

old-coderEvidence-first development — surround the implementation with an executable spec and a gauntlet of constraints (tests, types, coverage, mutation) so line-by-line review becomes optional. Use when the user explicitly asks for high-assurance or evidence-first work ("reliable", "TDD", "prove it works", "I won't read the code"), or when the change touches high-stakes domains (money, auth, data loss, concurrency, public API). For routine changes where the user just wants normal tests, write good tests directly instead of invoking this loop.Security

SharePost on X LinkedIn