iterate-pr

Diagnose GitHub pull request failures, apply validated fixes, and monitor checks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill coordinates the repetitive cycle of diagnosing pull request failures, applying fixes, presenting changes for user approval, and monitoring subsequent checks without pushing code on the user's behalf.

Core Features & Use Cases

  • Failure Diagnosis: Inspect PR checks, CI logs, review comments, and issue discussions to identify the first actionable problem.
  • Validated Fixes: Implement focused fixes, run relevant local verification, and route nontrivial changes through review.
  • Iterative Monitoring: Wait for the user to push, monitor the retained pull request, reassess all checks, and repeat only when concrete progress is possible.
  • Use Case: When a pull request fails linting and receives review feedback, use this Skill to address one failure category at a time, present the validated changes, and continue monitoring after the user pushes.

Quick Start

Ask the iterate-pr skill to inspect pull request 123, fix its first actionable CI failure, and guide the next iteration without pushing changes.

Frequently Asked Questions about iterate-pr

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

FAQPage Schema
How do I fix failing GitHub pull request checks and handle review feedback?

To fix failing GitHub pull request checks, diagnose CI failures and reviewer comments, apply focused local fixes, validate them, and monitor subsequent checks through an iterative approval workflow.

What is the best way to automate pull request failure diagnosis and fix validation?

Automating pull request failure diagnosis involves inspecting CI logs and discussions to identify the first actionable problem, implementing a fix, running local verification, and presenting changes for user approval.

Can I use workflow automation to resolve flaky CI failures without pushing code directly?

Yes, you can resolve flaky CI failures through a controlled loop that diagnoses issues, validates fixes locally, and requires user approval before pushing, ensuring you maintain direct push control.

How do I iterate on pull request issues when checks fail repeatedly?

Iterating on pull request issues requires reassessing all checks after a user push, addressing one failure category at a time, and repeating the validation and presentation cycle only when concrete progress is possible.

Does this approach support addressing pull request review comments and linting failures one at a time?

Yes, this approach supports addressing pull request review comments and linting failures by isolating one failure category at a time, applying validated fixes, and guiding the next iteration after user approval.

What do I need to start resolving pull request failures with a no-push approval workflow?

To start resolving pull request failures, you need GitHub pull request evidence, check-status inspection capabilities, CI and discussion analysis, and local verification tools to route nontrivial changes through review.