v1.0 to v1.0

---

name: qodoloop

description: >

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".

compatibility: Requires git and gh (GitHub CLI) authenticated, with Qodo Merge installed on the repo.

metadata:

version: "1.0"

allowed-tools: Bash(gh:*) Bash(git:*)

---

<!-- Generated by scripts/build-adapters.sh. Do not edit directly. -->

# 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.

Qodo runs as `qodo-code-review[bot]` and posts **two independent things** per review pass, not one:

**Use the inline threads as the source of truth.** They carry `isResolved` state natively (fetch via GraphQL, see `references/graphql-queries.md`), so "done" is answerable directly instead of re-parsing the rollup's HTML on every iteration. Each thread's body contains a `<details><summary>Agent Prompt</summary>` (or `**Agent Prompt**`) section with a ready-made fix spec, and a severity badge image whose `alt` text is `Remediation recommended` or `Informational` (recommended ↔ "Review recommended", informational ↔ "Optional").

## Instructions

### 1. Identify the PR

```bash

gh pr view --json number,headRefName,headRefOid -q '{number, branch: .headRefName, sha: .headRefOid}'

```

Check out the branch if not already on it, **then require a clean working

tree** (`git status --porcelain` empty) before touching anything:

```bash

```

This is the precondition step E's scoped `git add <file>` depends on: staging

only the files a fix touched is safe *because* the tree started clean, so

nothing else could be sitting in those files. Skip this check and a file

with pre-existing local edits will have those edits swept into the fix

narrower.

### 2. Loop (max 5 iterations)

#### A. Wait for a review of the current head

```bash

SINCE=$(date -u +%Y-%m-%dT%H:%M:%SZ)

git push

```

Poll (every ~10s, timeout ~5min), fetching **every page** of comments, not just the first:

```bash

gh api --paginate "repos/{owner}/{repo}/issues/<PR_NUMBER>/comments?per_page=100" | jq -s '

add | map(select(.user.login == "qodo-code-review[bot]")) | sort_by(.created_at)'

```

- Any of them contains "review limit" or "paused" → **stop the loop now**, go to Report with `blocked: rate-limited`.

- The latest one starts with `<h3>Code Review by Qodo</h3>` → proceed to step B.

- Otherwise (nothing yet, or only "Qodo is busy working") → sleep 10s and poll again, up to the 5-minute timeout.

#### B. Fetch unresolved findings

Build the working set: all `recommended` threads, plus `optional` ones too if `--include-optional`.

#### C. Check exit conditions

Stop if the working set is empty, or max iterations reached.

#### D. Fix each finding

#### E. Commit and push

```bash

git add <files touched by this iteration's fixes>

git commit -m "address Qodo review feedback (qodoloop iteration N)"

git push

```

#### F. Answer each finding

- **Fixed** findings: reply with one or two sentences (what you changed and why), **then** resolve:

```bash

gh api graphql -f query='

mutation($threadId: ID!, $body: String!) {

addPullRequestReviewThreadReply(input: {pullRequestReviewThreadId: $threadId, body: $body}) {

comment { id }

}

}' -f threadId="$THREAD_ID" -f body="$REPLY_TEXT"

```

Go back to step A.

### 3. Report

| Field | Value |

|--------------------|-------|

| Iterations | N |

| Findings resolved | N |

| Findings blocked | N (with reasons, left unresolved) |

| Remaining | N (if any) |

| Blocked | rate-limited / human-intervention / max-iterations / none |

```text

Qodoloop complete.

Iterations: 2

Resolved: 4 (fixed, replied + resolved)

Blocked: 1 (needs a human call, replied, left unresolved)

Remaining: 0

```

## References