review-loop

Solid

Bounded review-apply-resolve convergence loop for a GitHub PR (draft PRs are fine). Runs up to N=5 iterations of pr-reviewer → implement-suggestion (--resolve-all) → polish simplify, converging until every review thread is resolved — through a fix OR a reply (answered question, recorded rationale) — so the PR is left with zero open threads (only genuine human-judgment flags stay open). On convergence it also refreshes the PR description to match the shipped diff and, best-effort, notes the linked Linear ticket. Use after opening a draft PR to converge the branch to a clean, review-ready state before undrafting. Also converges CI: after each iteration's push it reads the check state and delegates a red mechanical failure to ci-auto-fix, so convergence means zero open threads AND CI not red (--no-ci opts out; create-pr and autonomous-workflow pass it because they own their own CI phase). On a UI PR it also runs the committed preview-spec block against the live preview deployment once at exit (report-only, never

Code & Development 13 stars 2 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 86/100

Stars 20%
38
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# review-loop — Bounded Review-Apply-Resolve Convergence Drive a PR from its initial draft state to a clean, review-ready state by iterating `pr-reviewer` → `implement-suggestion --resolve-all` → `polish simplify` until **every review thread is resolved** or the cap is reached, then refresh the PR description to match the shipped diff. A thread is resolved when it is **either fixed** (a code change landed) **or answered** (a reply — the answer to a question, the agent's take on a discussion, or a rationale for a declined suggestion). The only threads left open at convergence are genuine **human-judgment flags**: a real potential issue the agent will neither auto-apply nor honestly decline. That safety valve means the loop can never green-wash a PR by resolving a live finding — it surfaces it instead. This skill is an **orchestrator**. It contains no quality rules of its own. It sequences existing pieces, each owning its own domain: 1. `pr-reviewer` — finds issues (read-only; posts one `COMMENT` review; on a re-review resolves its own addressed threads). 2. `implement-suggestion --resolve-all` — applies actionable findings **and** replies-to-and-resolves the non-fix threads it can honestly close (single-shot, no `--watch`). 3. `Skill("polish", "simplify")` — applies Class M mechanical refactors behind a confidence gate. 4. `ci-auto-fix` — diagnoses and fixes a red check after the iteration's push (skipped under `--no-ci`). 5. On convergence — refreshes the PR description (...

Details

Author
mthines
Repository
mthines/agent-skills
Created
4 months ago
Last Updated
yesterday
Language
JavaScript
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

fix-pr-review-loop

Use when the user asks to fix a PR review and drive it to approval autonomously — "fix the PR review and loop until approved", "fix-pr-review-loop", "keep addressing review comments until this PR is approved", or as the standalone counterpart to work-on-issue-loop's polling/resolving steps for a PR that already exists. Takes an optional PR number/URL (defaults to the current branch's PR). Repeatedly calls fix-pr-review to resolve the latest review, waits for the resulting re-review from the selected review bot (@claude by default, @codex when selected), and repeats. Stops on a bare LGTM with nothing left to fix; once past 5 review cycles it stops at the first LGTM it sees even if non-blocking findings remain, rather than continuing to chase them.

49 Updated yesterday
richkuo
AI & Automation Listed

review-loop

Multi-round adversarial code review loop — four specialized agents (correctness, adversarial, API design, test rigor) run in parallel against a PR, repeated until all four return `CLEAN — ship it` or a budgeted number of rounds (default 5) is exhausted — whichever comes first, with two ask-first soft stops in between (a NIT-only round; severity declining two rounds straight) so the loop pauses to check in on diminishing returns instead of always running to the cap. Use when the user wants a thorough review of a substantive PR — new interfaces, contract changes, load-bearing refactors — and has signalled they want both correctness AND polish. Heavy: up to 5 rounds × 4 agents = 20 sub-invocations, so not for tiny bug fixes, WIP sketches, or doc-only PRs. Invoke explicitly; do not auto-trigger from a generic "review this" request unless the user names the high-bar mandate.

10 Updated today
spxrogers
Code & Development Listed

review-loop

Work on PRs managed by Review Loop. Inspect status, coordinate fixes, and handle decisions, retries or cancellation using the repository's policy.

14 Updated today
BinaryBourbon