Agent skill · kevmoo
pr-loop
Autonomous pull request review loop that pushes code, polls for AI/bot review comments (e.g., Gemini Code Assist), surgically remediates feedback, commits, pushes, comments `/gemini review`, and loops until zero feedback remains. Requires the `github-pr-triage` skill.
What it needs
About 9k tokens when loaded.
What this skill does
Autonomous PR Review Loop (pr-loop) This skill defines the autonomous loop pattern for pair programming with an automated AI code review bot (such as gemini-code-assist, gemini-code-review, or similar PR review agents). 📦 Prerequisites & Skill Dependencies REQUIRED SKILL: github-pr-triage MUST be installed alongside pr-loop. pr-loop directly depends on binaries, scripts, and rule definitions provided by github-pr-triage (including triage.dart and githubcli.dart). When to use this skill Use this skill when asked to get into a review loop with an AI review agent on a pull request. Trigger when the user asks to "loop with gemini", "run the PR loop", "iterate on review comments until clean", or executes /goal pr-loop. 🔓 Upfront VCS Authorization & Safeguards NEVER GUESS Target PR or Branch: Agents MUST NEVER guess the target branch or pull request. If the active local branch or PR is ambiguous, unclear, or not explicitly confirmed by the user, the agent MUST pause and explicitly ask the user for clarification using the askquestion tool before initiating the loop or executing any git pushes or gh commands. Request Blanket Upfront Consent: When initiating pr-loop, the agent MUST first confirm the target feature branch and remote with the user using the askquestion tool, requesting blanket consent for autonomous commits and pushes for the duration of the loop. Autonomous Execution Scope: Once upfront consent is established, the agent is authorized to execute git commit and git push autonomously on every loop iteration on that specific feature branch (headRefName) to origin. Trunk Branch Prohibition: Committing or pushing directly to main, master, or protected trunk branches remains strictly prohibited. NO commit --amend: Modifying commit history via git commit --amend is strictly prohibited. Always create new, atomic commits for each review pass. NO Force Pushes: Force pushing (git push -f or --force-with-lease) is strictly prohibited under any circumstances. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills kevmoo/pr-loop