iterate-pr

Collect CI checks and review feedback to drive fixes until all checks pass.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/spike-land-ai/spike.land --skill iterate-pr-spike-land-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: iterate-pr
Source: https://github.com/spike-land-ai/spike.land/tree/main/.agents/skills/iterate-pr
Command: npx skills add https://github.com/spike-land-ai/spike.land --skill iterate-pr-spike-land-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Automatically iterates on a GitHub PR by collecting CI checks and review feedback, guiding targeted fixes until all checks pass.

Core Features & Use Cases

  • Automated CI status and log extraction from PR checks to identify failures.
  • Centralized feedback aggregation from reviews and inline threads, categorized by priority.
  • Deterministic fix loop: fetches failures, applies minimal edits, commits, and pushes until green.
  • Real-world use: when CI flakiness or requested changes require multiple cycles before merge.

Quick Start

From the repository root, run the iterate-pr skill to begin the feedback-fix-push-wait cycle until CI passes.

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 GitHub pull requests until CI checks pass?

Automating iterative PR workflows involves collecting CI checks and review feedback to drive targeted fixes. This Skill fetches failures, applies minimal edits, commits, and pushes until all GitHub checks pass.

What is the best way to aggregate review feedback and CI failures for a pull request?

Aggregating feedback centralizes reviews and inline threads, categorizing them by priority. It extracts CI status and logs from PR checks to identify failures, guiding minimal edits until the pull request passes.

Can I run automated pull request fixes from any directory in my repository?

Running automated pull request fixes requires executing from the repository root. The deterministic fix loop relies on included scripts to fetch CI checks and feedback, ensuring targeted edits apply correctly.

How does a deterministic fix loop handle flaky CI checks on a pull request?

A deterministic fix loop handles flaky CI by fetching failures, applying minimal edits, and pushing commits. It repeats this cycle until GitHub CI checks pass, requiring no manual intervention during the iteration process.

Do I need any external dependencies to automate my GitHub PR iteration workflow?

Automating your GitHub PR iteration workflow requires no external dependencies. It uses included scripts to fetch checks and feedback, running deterministic steps directly from the repository root.