← ClaudeAtlas

gh-gemini-review-looplisted

Use after a GitHub PR is opened, or when the user asks to handle gemini-code-assist review feedback, run the Gemini review loop, fix Gemini comments, or re-request Gemini review. Waits, fixes, pushes, re-asks. Capped by user preference, default 3 cycles.
OrenAshkenazy/gh-gemini-review-loop · ★ 3 · Code & Development · score 69
Install: claude install-skill OrenAshkenazy/gh-gemini-review-loop
# Gemini Code Assist PR Review Loop ## Overview Use this skill to run the full GitHub PR loop: after PR creation, wait for `gemini-code-assist` to finish reviewing, fetch unresolved actionable review threads, acknowledge the requested fixes, implement clear fixes, verify them, commit and push to the PR branch, and ask Gemini Code Assist to re-review the latest revision. Prefer thread-aware review data over flat PR comments. GitHub review threads preserve `isResolved`, `isOutdated`, file paths, line anchors, and diff hunks, which are necessary for reliable automation. ## Thread States Each Gemini review thread is in one of these states. The fetch script tags each thread accordingly, and the stop logic consumes the tag: - **`RESOLVED`** — Gemini or the maintainer has explicitly resolved the thread. Skip. - **`OUTDATED`** — The line anchor has moved out from under the thread (the code Gemini commented on no longer exists at that position). Auto-resolved by the script. Skip. - **`ADDRESSED_BY_REPLY`** — Unresolved, but the current user (or another maintainer) has posted a substantive reply (≥30 chars, not a bot, not a token "ack"). Treated as a human decision to defer/wontfix; the loop does not try to fix this thread again. The script auto-resolves these on the next pass via GraphQL (see "GitHub Write Safety" below). Opt out with `--no-resolve-addressed-by-reply`. - **`UNRESOLVED`** — Actionable. Drives the next fix attempt. A thread can transition `UNRESOLVED → ADDRESSED_