← ClaudeAtlas

review-looplisted

Cross-LLM iterative code review loop. Spawns a peer reviewer (Codex, Claude, or Gemini CLI) to review code changes, then iterates until both agents agree on the final code state. Code gets modified during the loop — the final output is improved code + consensus report. Use when: "review loop", "peer review", "cross review", "review with codex", "review with claude", "review with gemini", "让 codex review", "让 claude review", "交叉 review", "peer review 这段代码", "code review loop", "iterative review"
stone16/harness-engineering-skills · ★ 26 · Code & Development · score 85
Install: claude install-skill stone16/harness-engineering-skills
# Review Loop — Cross-LLM Iterative Code Review Spawns a peer reviewer (Codex, Claude, or Gemini) to independently review your code changes. The host agent evaluates findings, implements accepted fixes, and re-submits for peer re-review. Iterates until both agents agree on the final code state. **Key**: You (the human) do NOT need to participate. Watch progress via `.review-loop/<session>/rounds.json` and `summary.md`. **Compatibility note**: `rounds.json` keeps the historical field name `claude_actions` for backward compatibility. In Codex-hosted runs, that field still stores the host agent's decisions and code changes. ## Prerequisites - **Required**: `git` CLI - **Peer (one of)**: `codex` CLI (`codex --version`), `claude` CLI (`claude --version`), or `gemini` CLI (`gemini --version`) - **Optional**: `gh` CLI (for PR scope detection) ## Configuration ### Defaults | Setting | Default | Options | |---------|---------|---------| | `peer_reviewer` | `codex` | `codex`, `claude`, `gemini` | | `max_rounds` | `5` | 1–10 | | `timeout_per_round` | `600` | seconds | | `scope_preference` | `auto` | `auto`, `diff`, `branch`, `pr` | | `read_only` | `false` | `true` = report-only, no code changes | The peer reviewer always runs with local repository access. **Read-only mode** (`read_only: true`): Peer reviews code and the host agent evaluates findings, but NO code changes are made. Output is a findings report only — no fix commits, no code evolution loop. Useful when review-loop