---
name: appwrite-review-loop
description: Iteratively improves a GitHub pull request until Appwrite Review grades it Tier S (ready to merge) with zero unresolved comments. Triggers a review, fixes actionable findings, pushes, and repeats. Use when the user wants to clear Appwrite Review's comments, reach Tier S, loop on review comments, or run review-loop.
title: appwrite-review-loop
canonical_url: https://skilld.dev/gh/appwrite/skills/appwrite-review-loop
last_updated: 2026-11-18T21:00:56.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install appwrite/skills/appwrite-review-loop`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/appwrite-review-loop`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/appwrite/skills/appwrite-review-loop) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/appwrite-review-loop`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/appwrite-review-loop --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/appwrite-review-loop --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Appwrite Review loop

Fix a pull request until Appwrite Review grades it **Tier S** (ready to merge) and leaves no unresolved comments.

Each review counts toward the Appwrite project's review usage. Do not request a new review when the current head already has a finished review from Appwrite Review and you have not pushed anything since.

The command blocks are examples, written for git and the GitHub CLI. Run whatever this environment actually provides to do the same job, including commands the examples do not list. If `gh` or `git` is missing, or a command fails because of how this machine authenticates, try another client before stopping.

## Inputs

- **Pull request number** (optional). If omitted, use the pull request for the current branch.

## Instructions

### 1. Identify the pull request

Set `PR_NUMBER` when the user gave one. Leave it empty to use the current branch.

```bash
if [ -n "$PR_NUMBER" ]; then
  gh pr view "$PR_NUMBER" --json number,headRefName,headRefOid,url -q '{number: .number, branch: .headRefName, sha: .headRefOid, url: .url}'
else
  gh pr view --json number,headRefName,headRefOid,url -q '{number: .number, branch: .headRefName, sha: .headRefOid, url: .url}'
fi
```

Use the `number` from that JSON as `<PR_NUMBER>` in every later command. Check out `branch` if you are not already on it. Stop if there is no open pull request.

### 2. Find the summary and the mention handle

Appwrite Review keeps one issue comment per pull request up to date and edits it in place. Its body starts with the marker `<!-- appwrite-hansi:summary:<REPOSITORY_ID> -->`, where `<REPOSITORY_ID>` is the Appwrite Review repository that wrote it.

```bash
gh api --paginate "repos/{owner}/{repo}/issues/<PR_NUMBER>/comments?per_page=100" \
  --jq '.[] | select(.body | contains("<!-- appwrite-hansi:summary")) | {id, updated_at, body}'
```

There is usually one. Several Appwrite projects can review the same repository, and each writes its own summary. When there are several and the user did not say which project they mean, work with each one separately and say which is which. Never mix findings from two summaries.

The footer looks like `Comment <code>@app-name review</code> to re-run`. That `@<slug>` is Appwrite Review's mention handle on this repository; take it from inside the `<code>` tag. Review comments are authored by `<slug>[bot]`.

The `Hansi` check run of a summary is the one whose `external_id` is that summary's `<REPOSITORY_ID>`:

```bash
gh api "repos/{owner}/{repo}/commits/<HEAD_SHA>/check-runs?check_name=Hansi" \
  --jq '[.check_runs[] | select(.name == "Hansi" and .external_id == "<REPOSITORY_ID>")] | sort_by(.started_at) | last | {status, conclusion, head_sha, title: .output.title, summary: .output.summary, slug: .app.slug}'
```

A check run written before reviews were keyed by repository has no `external_id`. When no check matches, drop the `external_id` filter and use the latest `Hansi` check, but only when there is a single summary.

When several projects review the repository, ask the user which one to loop on, then use only that summary's `<REPOSITORY_ID>`. A push or a mention starts a review in every project; that is expected.

If there is no summary yet, read the slug from the `slug` field of a `Hansi` check on the pull request (drop the `external_id` filter). If you still cannot find a handle, ask the user. Do not guess, and do not mention a different bot.

### 3. Loop

Repeat the cycle below. **Stop after 5 iterations.**

#### A. Make sure a review of the current head is running

Push commits that are not on the remote yet:

```bash
git status --short --branch
git push
```

A push reviews the new commits on its own when automatic reviews are enabled (the default). Look at the `Hansi` check on the **current** head SHA, not an older one:

```bash
HEAD_SHA=$(gh pr view <PR_NUMBER> --json headRefOid -q .headRefOid)
gh api "repos/{owner}/{repo}/commits/$HEAD_SHA/check-runs?check_name=Hansi" \
  --jq '[.check_runs[] | select(.name == "Hansi" and .external_id == "<REPOSITORY_ID>")] | sort_by(.started_at) | last | {status, conclusion, started_at, title: .output.title, summary: .output.summary}'
```

A completed check for this head is the review to read. Do not request another one.

If this head has no `Hansi` check, wait about 30 seconds and look again. The webhook needs a moment after a push. Comment only if it is still missing. Skip the comment when `status` is `queued` or `in_progress`.

```bash
gh pr comment <PR_NUMBER> --body "@<slug> review"
```

The comment must be plain text. A mention inside a code span or a quote does not start a review.

Poll until that check completes. Reviews read the repository, so allow about 15 minutes (90 attempts, 10 seconds apart):

```bash
ATTEMPTS=0
MAX_ATTEMPTS=90
while true; do
  ATTEMPTS=$((ATTEMPTS + 1))
  if [ "$ATTEMPTS" -gt "$MAX_ATTEMPTS" ]; then
    echo "Timed out waiting for the Hansi check." >&2
    exit 1
  fi
  CHECK=$(gh api "repos/{owner}/{repo}/commits/$HEAD_SHA/check-runs?check_name=Hansi" \
    --jq '[.check_runs[] | select(.name == "Hansi" and .external_id == "<REPOSITORY_ID>")] | sort_by(.started_at) | last')
  STATUS=$(printf '%s' "$CHECK" | jq -r '.status // empty')
  if [ -z "$STATUS" ]; then
    echo "Waiting for the Hansi check to appear..."
    sleep 10
    continue
  fi
  if [ "$STATUS" = "completed" ]; then
    printf '%s' "$CHECK" | jq -r '"Hansi check completed: \(.conclusion) — \(.output.title)"'
    break
  fi
  echo "Waiting for the Hansi check... ($STATUS)"
  sleep 10
done
```

Stop the loop, and do not use an older review, when:

- polling times out
- `conclusion` is `skipped` (drafts, disabled reviews, or a base branch Appwrite Review does not review)
- the check title is `Review failed`

`failure` means Appwrite Review requested changes. `neutral` means it commented. Both are finished reviews: keep going and read the comments.

#### B. Read the review

Fetch the summary comment again (the command in step 2). Appwrite Review edits that same comment in place. Parse:

- **Tier**, from the heading `Tier S` through `Tier F`. **S** means ready to merge. Open findings cap it: a minor finding means at most **A**, a major one at most **B**, a critical one at most **D**. Informational notes do not lower it.
- **Verdict table**: new comments, fixed, and still open.
- **Findings table** of comments posted on this review. A row is a title plus a file and line.
- **Still open from earlier reviews**, inside the `⏳ Still open from earlier reviews` details block.
- **Filtered out**, inside the `🔇 Filtered out` details block. These were considered and not posted. Include the reason.
- **Approval withheld**, a `> [!NOTE]` block. Appwrite Review will not approve in that case. A note about an open bug finding clears once that finding is fixed or dismissed. A note about write access or an incomplete diff does not.

Then read the threads.

List unresolved review threads and keep the ones whose first comment is from `<slug>[bot]`:

```bash
gh api graphql -f query='
query($cursor: String) {
  repository(owner: "OWNER", name: "REPO") {
    pullRequest(number: PR_NUMBER) {
      reviewThreads(first: 100, after: $cursor) {
        pageInfo { hasNextPage endCursor }
        nodes {
          id
          isResolved
          comments(first: 20) {
            nodes { databaseId body path author { login } }
          }
        }
      }
    }
  }
}'
```

Page with `endCursor` while `hasNextPage` is true. A finding comment starts with a bold title, then the explanation, sometimes a `suggestion` block, and a footer like `Major · bug`. When several projects review the repository, all of their findings come from the same bot account: match a thread to a summary by its title in that summary's findings tables.

Also read the latest review body from Appwrite Review. If GitHub rejected the inline comments, the findings are in that body instead of threads. Treat those as open too.

#### C. Stop when the pull request is clean

Stop when **all** of these are true:

- The tier in the current summary is **S**
- Appwrite Review has **no unresolved threads**, and the summary has no findings still open
- You are not waiting on a review of commits you just pushed

Then, if the latest `Hansi` check on this head is `failure` (the pull request is still in "changes requested"), request **one** `@<slug> review` and wait for it, so Appwrite Review can submit the approval. Do not repeat that extra review. If the follow-up still does not approve, stop and report the summary note. A withheld approval or `reviews.approve: false` in `.hansi.json` will not become an approval.

Also stop when the fifth iteration finishes. Report whatever is left.

#### D. Fix what Appwrite Review asked for

For each unresolved Appwrite Review finding:

1. Read the file, the diff hunk, and the comment.
2. Fix it in the code when it describes a real bug. Apply a suggestion block only when it actually fixes that bug.
3. When the comment does not apply, reply on **that thread** with a short reason. A reply to a finding is enough; you do not need to mention Appwrite Review again. Appwrite Review answers, and dismisses the finding when it agrees.

```bash
gh api "repos/{owner}/{repo}/pulls/<PR_NUMBER>/comments/<COMMENT_ID>/replies" -f body='...'
```

Do **not** call `resolveReviewThread` yourself. Resolving a thread in GitHub leaves the finding open in Appwrite Review's summary, so the tier stays capped. Appwrite Review resolves the thread when a later review sees the fix, or when it dismisses the finding after your reply.

#### E. Wait for replies before reviewing again

If you replied on any thread, wait until Appwrite Review has answered (it reacts with 👀, then comments) or about 5 minutes have passed. A dismissal updates the summary comment. Read it again before you decide the iteration still needs code changes.

#### F. Commit and push code changes

If you changed files, commit only those files. Leave unrelated work unstaged.

```bash
git add path/to/file
git commit -m "Address Appwrite Review feedback (iteration N)"
git push
```

Go back to step **A**. The push starts the next review; do not also comment `@<slug> review` unless that check never appears.

If the only action was thread replies and nothing remains open, go back to step **C** without pushing an empty commit.

### 4. Report

After the loop, summarize:

```
review-loop complete.
  Pull request:  #123
  Iterations:    2
  Tier:          S
  Resolved:      4 comments
  Remaining:     0
```

When the loop stops early:

```
review-loop stopped after 5 iterations.
  Pull request:  #123
  Tier:          A
  Resolved:      6 comments
  Remaining:     1

Remaining issues:
  - src/auth.ts:45 — "Session cookie is not marked HttpOnly"
```

Include the pull request URL. If Appwrite Review withheld approval, say so in the report even when the tier is **S** and nothing is left open.
