Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Autonomous PR review loop with Greptile. Use when an agent creates a PR and needs to autonomously handle code review feedback — reading Greptile reviews, fixing issues, pushing fixes, re-triggering review, and auto-merging when score is 4/5+. Trigger on commands like "pr review {url}", "review my PR", or when a Greptile review webhook/poll delivers feedback.
Autonomous PR review loop with Greptile. Use when an agent creates a PR and needs to autonomously handle code review feedback — reading Greptile reviews, fixing issues, pushing fixes, re-triggering review, and auto-merging when score is 4/5+. Trigger on commands like "pr review {url}", "review my PR", or when a Greptile review webhook/poll delivers feedback.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Autonomous cycle: Greptile reviews PR → agent fixes feedback → pushes → re-triggers → repeats until score ≥ 4/5 or max rounds.
When triggered with a PR URL or review payload: # Run the review loop bash scripts/pr-review-loop.sh <owner/repo> <pr-number> Or invoke steps manually — see below.
# Get latest Greptile review gh api "/repos/{owner}/{repo}/pulls/{pr}/reviews" \ --jq '[.[] | select(.user.login == "greptile-apps[bot]")] | last' # Get inline comments gh api "/repos/{owner}/{repo}/pulls/{pr}/comments" \ --jq '[.[] | select(.user.login == "greptile-apps[bot]")]'
Look for confidence/quality score in review body. Greptile typically includes a score like Score: X/5 or Confidence: X/5. Extract it: Score ≥ 4/5 → auto-merge Score < 4/5 → fix issues No score found → treat as needing fixes if there are comments, otherwise merge
gh pr merge <number> --merge --delete-branch --repo <owner/repo>
Maintain review-state.json in workspace: { "owner/repo#123": { "rounds": 2, "maxRounds": 5, "lastScore": 3, "sameScoreCount": 1 } } Update after each round. Check exit conditions: rounds ≥ 5 → merge anyway, notify Master sameScoreCount ≥ 2 (same score 2 rounds in a row) → merge anyway, notify Master
Architectural decisions (review mentions architecture, design patterns, breaking changes) → ping Master on Telegram, don't auto-fix Max rounds reached → merge + notify Master with summary Unclear feedback → ask Master
Agents should respond to: pr review <url> — start review loop on a PR pr review <owner/repo#number> — same, by reference pr status — show active review loops and their state
See references/greptile-patterns.md for common Greptile feedback patterns and fix strategies.
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Largest current source with strong distribution and engagement signals.