coderabbitlooplisted

Iteratively drives a GitHub PR to zero unresolved CodeRabbit (coderabbitai[bot]) findings. Reads each inline comment's own "Prompt for AI Agents" block (CodeRabbit's ready-made fix spec per issue), applies the fix, replies to the thread explaining what was done, resolves it, pushes, and re-triggers CodeRabbit. Repeats until clean or a real blocker needs a human. Use when the user wants a PR fully addressed against CodeRabbit's review, or says "run coderabbitloop" / "satisfy CodeRabbit" / "resolve CodeRabbit comments".
oleg-koval/agent-skills · ★ 3 · AI & Automation · score 75

Install: claude install-skill oleg-koval/agent-skills

# Coderabbitloop Fix every actionable CodeRabbit finding on a PR, answer each thread, resolve it, and keep going until CodeRabbit has nothing left to say (or a finding needs a human call). ## Inputs - **PR number** (optional): detect from the current branch if not given. ## How CodeRabbit actually posts (verified against docs.coderabbit.ai and a live install: don't assume otherwise) CodeRabbit runs as `coderabbitai[bot]` and posts **two independent things**, not one: 1. An auto-generated **walkthrough/summary issue comment**: body starts with the HTML marker ``. This is a description, not a review: use it for context only, never as a source of fixable findings. 2. A **formal PR review** carrying one **inline review comment per finding**, each a real, resolvable GitHub review thread at the finding's file/line. Each one contains a `<details><summary>🤖 Prompt for AI Agents</summary>` block: a ready-made fix spec, CodeRabbit's own words, meant to be handed straight to an agent. **Use the inline threads as the source of truth**, exactly like Greptile/Qodo: fetch via GraphQL `reviewThreads`, which carries native `isResolved` state (see `references/graphql-queries.md`, shared with `qodoloop`; only the bot login and the prompt-heading text differ). CodeRabbit has slash commands (official, `docs.coderabbit.ai/reference/review-commands`)