iterate-pr

Iterate pull requests by resolving CI failures and review feedback until validation succeeds.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the repetitive cycle of fixing pull request issues, responding to review feedback, and waiting for CI results so developers can reach a merge-ready state faster.

Core Features & Use Cases

  • CI Failure Iteration: Collects GitHub Actions check results, extracts failure details, and guides root-cause fixes before pushing updates.
  • Review Feedback Handling: Fetches and categorizes PR comments using priority levels, helping address required and recommended changes systematically.
  • Use Case: A developer with a failing pull request can use this Skill to analyze checks, apply fixes, monitor new runs, and continue iterating until all validations pass.

Quick Start

Use the iterate-pr skill to review the current pull request, fix failing checks, address feedback, and continue until CI 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 failing GitHub Actions checks on a pull request?

You can automate resolving CI failures by collecting GitHub Actions check results, extracting failure details, and guiding root-cause fixes before pushing updates. This pull request iteration process repeats until all validations pass.

How do I systematically address code review feedback on a GitHub pull request?

Address code review feedback by fetching and categorizing PR comments using priority levels. This helps systematically resolve required and recommended changes before pushing updates for a merge-ready state.

Do I need the GitHub CLI to automate pull request iteration?

Yes, you need GitHub CLI access to automate pull request iteration. The bundled scripts require repository-root execution to monitor checks, analyze feedback, and respond to review threads.

What is the best way to keep a pull request moving until CI passes?

The best way to keep a PR moving is automating the repetitive cycle of fixing issues, responding to feedback, and waiting for CI results. This guides root-cause fixes and monitors new runs until validation succeeds.

Can I automate responding to GitHub review threads during CI failure iteration?

Yes, you can automate responding to review threads during CI failure iteration. The process fetches review feedback, categorizes comments by priority, and responds systematically while monitoring check runs.

Why does my automated pull request validation keep failing after pushing updates?

Automated pull request validation may keep failing if root-cause fixes are not properly applied before pushing updates. Analyzing extracted GitHub Actions failure details ensures the correct fixes are made before monitoring new runs.