AcostaDDev

My Harness — Git skill for Claude Code

Git community

Local application that orchestrates Codex and Claude Code agents to plan, implement, review and commit tasks in Git repositories.

How to install My Harness

This entry records only its repository, not the path inside it, so there is no exact command to give. Open AcostaDDev/my-harness and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What My Harness does

Local application that orchestrates Codex and Claude Code agents to plan, implement, review and commit tasks in Git repositories.

Alternatives in Git

  • Async Code — GitHub Repo stars Use Claude Code/CodeX CLI to perform multiple tasks in parallel Parallel task execution 513 ★
  • Operator OSS — Run many Claude Code (or Codex) sessions in parallel — across every project — from one screen 202 ★
  • Lore — git memory for coding agents — a local, searchable archive of your Claude Code and Codex sessions 142 ★

README

My Harness

My Harness is a local application that runs a development harness with AI coding agents over your own Git repositories. A **reviewer** agent plans and reviews in read-only mode; an **executor** agent is the only writer. The harness validates every change with your project's own commands, binds the review to the exact content, and makes the commit itself. Work is organized in phases and bounded tasks, with project documentation, chat, metrics and recovery after crashes. Everything runs on your machine: the service listens only on `127.0.0.1`, and the models are reached through the official Codex and Claude Code CLIs with your own account.

[Leer en español](README.es.md)

Status

  • Pre-release. The first local version is complete within the scope described below; the package declares version 0.1.1, a patch of the first public release 0.1.0, and is not published on PyPI. See the changelog for the versioning policy.
  • Platform. Only macOS on Apple silicon (ARM64) has been tested. Other platforms are not characterized.
  • Evidence. The offline test suites use temporary Git repositories, SQLite and fake agents. Real runs with providers exist only for the capabilities marked as such in Supported scope.
  • First use. The guided installation and both project entries are rehearsed with an installed wheel, fake clients/tools and temporary Git/SQLite on macOS ARM64. Setup uses the browser form; project operations use protected HTTP. Chrome was checked in English/Spanish, light/dark themes, desktop (1280/1470 px) and mobile (390 px; setup also 320 px), with sampled Tab/Enter navigation. Other browsers, screen readers, a complete keyboard audit and every size/theme/language combination are untested. These checks do not qualify real provider calls, other platforms or the next public candidate.
  • Guided configuration. Installation/start scripts, global setup, own project profiles,