iterate-pr

Automate CI failure fixes and code review feedback on GitHub pull requests.

Updated May 5, 2026
One-click install
npx skills add https://github.com/iani-kuli/harness_bro --skill iterate-pr-iani-kuli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: iterate-pr
Source: https://github.com/iani-kuli/harness_bro/tree/main/.claude/skills/ported/iterate-pr
Command: npx skills add https://github.com/iani-kuli/harness_bro --skill iterate-pr-iani-kuli

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, uv, and includes scripts (resource) components.

What problem does it solve?

This Skill solves the repetitive and time-consuming cycle of monitoring CI checks, gathering review feedback, and manually pushing fixes to get a Pull Request merged.

Core Features & Use Cases

  • Automated CI Monitoring: Continuously polls CI status and extracts failure snippets from logs to identify root causes.
  • Feedback Categorization: Automatically fetches and categorizes PR review comments using the LOGAF scale to prioritize high-impact fixes.
  • Workflow Orchestration: Manages the feedback-fix-push-wait cycle, allowing the AI to handle CI failures and review requests autonomously.

Quick Start

Use the iterate-pr skill to monitor the current pull request and automatically address all high and medium priority feedback until the build is green.

Frequently Asked Questions about iterate-pr

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

FAQPage Schema
How do I automate fixing CI failures on a GitHub pull request?

Automate fixing CI failures on a GitHub pull request by polling CI status, extracting failure snippets from logs, and categorizing review comments to guide targeted code modifications autonomously. This orchestrates the feedback-fix-push-wait cycle until the build is green.

How does LOGAF scale categorization work for PR review comments?

LOGAF scale categorization for PR review comments works by automatically fetching feedback and categorizing it to prioritize high and medium impact fixes. This allows the system to address the most critical code review feedback first during the iteration loop.

Do I need the GitHub CLI and uv package manager to automate PR feedback loops?

Yes, you need the GitHub CLI for authentication and the uv package manager to automate PR feedback loops. These dependencies are required to execute the diagnostic and monitoring scripts that poll CI status and parse failure logs.

What is the best way to handle repetitive code review feedback and CI monitoring?

The best way to handle repetitive code review feedback and CI monitoring is using a workflow orchestration skill that autonomously manages the feedback-fix-push-wait cycle. It continuously polls CI status and categorizes review comments to push fixes until the PR is merged.

What are the limitations of automating pull request iterations?

Limitations of automating pull request iterations include the dependency on GitHub CLI authentication and the uv package manager for executing scripts. The automation focuses on high and medium priority feedback, meaning lower priority review comments may not be addressed autonomously.