qodolooplisted

Iteratively drives a GitHub PR to zero unresolved Qodo (qodo-code-review[bot]) findings. Reads each finding's own "Agent Prompt" (Qodo hands you a ready-made fix spec per issue), applies the fix, replies to the thread explaining what was done, resolves it, pushes, and waits for Qodo's next pass. Repeats until clean or a real blocker needs a human. Use when the user wants a PR fully addressed against Qodo's review, or says "run qodoloop" / "satisfy Qodo" / "resolve Qodo comments".
oleg-koval/agent-skills · ★ 3 · AI & Automation · score 75

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

# Qodoloop Fix every actionable Qodo finding on a PR, answer each thread, resolve it, and keep going until Qodo has nothing left to say (or a finding needs a human call). ## Inputs - **PR number** (optional): detect from the current branch if not given. - **Include optional findings** (optional, default off): Qodo tags each finding "Review recommended" (actionable) or "Optional" (informational/lower-confidence). By default only "Review recommended" findings count toward done; pass `--include-optional` to also fix and resolve the optional ones. ## How Qodo actually posts (verified against a live install: don't assume otherwise) Qodo runs as `qodo-code-review[bot]` and posts **two independent things** per review pass, not one: 1. A rollup **issue comment** titled `<h3>Code Review by Qodo</h3>`: human-readable, all findings in one place. A separate `<h3>PR Summary by Qodo</h3>` comment is a plain description, not a review: ignore it. While running, Qodo posts `<h3>Qodo is busy working</h3>` as its own comment (not an edit of a prior one). 2. A **formal PR review** (`state: COMMENTED`) carrying one **inline review comment per finding**, each a real, resolvable GitHub review thread at the finding's file/line: same machinery as any human inline comment. **Use the inline threads as the source of truth.** They carry `isResolved` state natively (fetch via GraphQL, see `references/graphql-queries.md`), so "d