pr-fix-loop

Resolve GitHub pull request review issues by repeatedly applying fixes until merge.

1|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/hirokimry/vibecorp --skill pr-fix-loop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-fix-loop
Source: https://github.com/hirokimry/vibecorp/tree/main/skills/pr-fix-loop
Command: npx skills add https://github.com/hirokimry/vibecorp --skill pr-fix-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual churn of chasing PR feedback across comments, CI failures, and follow-up review cycles. It keeps a pull request moving until it is merged, closed, or escalated with a clear reason.

Core Features & Use Cases

  • Synchronous review remediation: Repeatedly checks PR state and applies the next round of fixes without relying on asynchronous wakeups.
  • Review and CI handling: Responds to requested changes, waits for review transitions, and tracks merge readiness.
  • Controlled escalation: Stops safely when merge conflicts, drafts, rate limits, or timeout and iteration limits are reached.
  • Use case: A teammate receives review comments plus failing CI on a PR and needs the AI to keep repairing the branch until the PR is ready to merge.

Quick Start

Ask the assistant to run pr-fix-loop on the current pull request or a specific PR URL and continue fixing review issues until the PR is merged or escalation is needed.

Frequently Asked Questions about pr-fix-loop

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically fix GitHub pull request review comments and CI failures?

You can automatically fix GitHub pull request review comments and CI failures by running a synchronous remediation loop that repeatedly checks PR state, applies the next round of fixes to review issues, tracks merge readiness, and waits for CI transitions until the PR is merged.

What is synchronous PR review remediation and how does it work?

Synchronous PR review remediation repeatedly checks the pull request state and applies the next round of fixes without relying on asynchronous wakeups, continuously cycling through review feedback and CI failures until the PR reaches a merged, closed, or escalated state.

How do I handle PR escalation when merge conflicts or rate limits occur?

To handle PR escalation safely during merge conflicts, draft states, rate limits, or timeout and iteration limits, the remediation loop stops automatically and escalates with a clear reason rather than forcing changes, ensuring safe handling of blocked pull requests.

Does this PR fix loop work with worktree-based teammate workflows?

Yes, this PR fix loop applies to worktree-based teammate workflows, allowing a teammate receiving review comments and failing CI on a PR to have the AI keep repairing the branch within the worktree until the PR is ready to merge.

What are the limitations of automating pull request review cycles?

Limitations of automating pull request review cycles include stopping safely when merge conflicts, draft states, rate limits, or predefined timeout and iteration limits are reached, requiring escalation handling rather than continuing to force fixes indefinitely.