← ClaudeAtlas

reviewlooplisted

Use when a PR has feedback from MORE than one reviewer — any mix of bots (Greptile, CodeRabbit, Copilot, linters) and human teammates — and the user wants every reviewer driven to a clear state, not just one specific bot. Use when the user says "clear all the reviews", "address every reviewer", "loop until the PR is clean", or wants bot reviews re-triggered and re-checked automatically.
BiswaViraj/agent-skills · ★ 0 · Code & Development · score 78
Install: claude install-skill BiswaViraj/agent-skills
# Reviewloop Drive a PR to **all-clear** across *every* reviewer — each bot AND each human — then loop until nothing actionable remains. **Core principle:** A bot is a pure function you can re-invoke (re-trigger → poll → read verdict). A human is async and uncontrollable. So **bots loop; humans get one pass and then you hand back.** Never block the loop waiting on a person. ## When to use - A PR has comments from several reviewers and you want them all resolved in one driven pass. - The reviewers are a mix you can't name up front — "address whatever's on the PR." - You want bot reviews **re-triggered** after each fix, not just read once. **When NOT to use:** You just want a one-shot read of what's outstanding with no loop and no re-triggering — that's a plain review-check, not this. ## The reviewer registry (the spine) No uniform code path covers all reviewers. Each needs four things — detect it, re-trigger it, read its verdict, know when it's done: | Reviewer | Detect (by login) | Re-trigger | Read verdict | Done-condition | |---|---|---|---|---| | **Greptile** | `greptile-apps` (CI check + bot review) | comment `@greptile review` | `N/5` confidence in PR body / its review | `5/5` **and** its threads resolved **and** check `success` | | **CodeRabbit** | `coderabbitai` | comment `@coderabbitai full review` | walkthrough + inline actionable comments (no score) | zero unresolved actionable CodeRabbit threads | | **Copilot** | `copilot-pull-request-reviewer` / `Copilot`