{"repo":"stone16/harness-engineering-skills","free":true,"listed":false,"github":"https://github.com/stone16/harness-engineering-skills","clone":"git clone https://github.com/stone16/harness-engineering-skills.git","description":"Run AI coding agents unattended for hours and ship PRs worth merging. Cybernetics-based multi-agent orchestration + cross-LLM peer review for Claude Code, Codex, and Gemini. Engine-enforced gates, fresh agent per checkpoint, cross-vendor review before every PR.","language":"Shell","stars":31,"topics":["ai-code-review","claude","claude-code","claude-code-plugin","code-quality","code-review","codex","developer-tools","gemini","peer-review"],"license":"Apache-2.0","category":"dev-tools","readme_excerpt":"English 中文 Harness Engineering Skills Stometa's public curated Claude Code skillset — a small, opinionated set of skills we use ourselves, published periodically. At a glance What it is : A Claude Code plugin with two engineering skills — review-loop (cross-model code review) and harness (multi-agent task orchestration). This repository is their public canonical source; changes are reviewed and released here. What it does : Coordinates a Plan → Generate → Evaluate → Retro pipeline with hard, engine-enforced constraints: two isolated sessions, a fresh sub-agent per checkpoint, an engine script as the sole gatekeeper, and a cross-vendor peer review before any PR lands. What problems it solves : Failure mode How it shows up What Harness does --- --- --- Context drift Planning, coding, and review share one growing context — the model drifts further with each turn Two-session split + fresh sub-agent per checkpoint (eigenbehavior reset) Self-certification The LLM that wrote the code also judges whether it passes Engine script rejects any pass-checkpoint where the evaluator session id matches a prior checkpoint in the same task Echo-chamber review The same model reviews its own work and misses its own blind spots review-loop enforces a different-vendor peer (Codex or Gemini) and runs a fresh-session final approval before closing Workflow at a glance Two phases, hard context boundary between them. Each phase contains its own fresh-sub-agent iteration loop. The engine script is the on","default_branch":null,"files":null,"tree":[],"storefront":"/r/stone16","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/stone16/harness-engineering-skills/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}