Chachamaru127/claude-code-harness

Claude Code Dedicated Development Harness - Achieving High-Quality Development Through an Autonomous Plan→Work→Review Cycle

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 34 minutes ago
Added to GitGenius on May 28th, 2026
Created on December 12th, 2025
Open Issues & Pull Requests: 10 (+0)
GitHub issues: Enabled
Number of forks: 299
Total Stargazers: 3,112 (+0)
Total Subscribers: 11 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

Claude Code Harness is a development workflow tool that enforces a structured plan-work-review-release cycle for AI-assisted coding with Claude, Codex, Cursor, and Grok.

The tool addresses the problem of drift in agent-driven development, where plans exist only in chat history, testing becomes optional under pressure, and review happens after code is merged. Rather than making the underlying model smarter, it establishes a repeatable procedure with clear boundaries around the model's output. The approach works through five core commands: plan converts intent into a spec and task list for human approval, work implements approved tasks with tests where needed, review examines results independently from implementation, sync detects drift between plan and actual code, and release packages verified evidence into changelogs and tags. Each stage produces material the next stage requires, creating a disciplined loop where human approval gates execution.

Developers should adopt this tool if they want to enforce accountability and traceability in AI-assisted projects, particularly when working with multiple AI coding assistants. It suits teams that need audit trails, want to prevent scope creep during implementation, or require independent review before merging. The tool is built around the constraint that written code is not the same as working code, and uses CI gates to verify that described features are actually wired and reachable.

The maintainers respond to issues and pull requests within a few days. Development activity centers on bug fixes, codex integration work, and enhancements.