iterate-pr

Automate GitHub PR iteration to fix CI failures and review feedback.

9|1|Updated Jan 15, 2016
One-click install
npx skills add https://github.com/wadackel/dotfiles --skill iterate-pr-wadackel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: iterate-pr
Source: https://github.com/wadackel/dotfiles/tree/main/home/programs/claude/skills/iterate-pr
Command: npx skills add https://github.com/wadackel/dotfiles --skill iterate-pr-wadackel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Iterates on a PR until CI checks pass and feedback is resolved, reducing manual back-and-forth.

Core Features & Use Cases

  • Automates PR iteration by checking CI status, collecting reviews, inspecting logs, and applying minimal fixes.
  • Coordinates GitHub CLI (gh) commands to surface actionable failures and guide the fix-push-cycle.
  • Use case: for PRs with flaky tests or multiple review rounds, the workflow streamlines retests and updates until green.

Quick Start

Start by selecting the current PR and initiating the automated iteration workflow to drive CI checks to 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 GitHub PR iteration until CI checks pass?

To automate PR iteration until CI passes, this Skill checks CI status, collects reviews, inspects logs, and applies minimal fixes. It coordinates the GitHub CLI to drive the fix-push-cycle, reducing manual back-and-forth until all checks are green.

Can I use GitHub CLI to automatically fix CI failures from pull request comments?

Yes, you can use GitHub CLI to automatically fix CI failures by running this Skill. It surfaces actionable failures and review feedback from PR comments, guiding deterministic fixes and pushing updates until all checks pass.

What is the best way to handle multiple review rounds and flaky tests on a pull request?

The best way to handle flaky tests and multiple review rounds is automating the PR iteration loop. This Skill streamlines retests and updates by coordinating CI checks and feedback, applying minimal fixes until the PR reaches a green state.

Do I need special repository permissions to automate pull request CI fixes?

Yes, you need repository permissions to view PRs, checks, and comments, along with the GitHub CLI installed. These permissions allow the automated iteration workflow to access logs and push fixes until CI checks pass.

Why does automated PR iteration stop before CI checks pass?

Automated PR iteration stops before CI passes if repository permissions are insufficient to view checks or comments, or if the GitHub CLI lacks access. It requires valid credentials to inspect logs and guide deterministic fixes through the fix-push-cycle.

Does the iterate-pr workflow work without GitHub CLI?

No, the iterate-pr workflow does not work without GitHub CLI. It requires the gh command-line tool to surface actionable CI failures and coordinate the automated fix-push-cycle until all pull request checks pass.