ralph-iterate

Automate one Ralph loop iteration to implement and commit the next ready GitHub issue from a milestone.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/fwojciec/quiver --skill ralph-iterate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralph-iterate
Source: https://github.com/fwojciec/quiver/tree/main/.claude/skills/ralph-iterate
Command: npx skills add https://github.com/fwojciec/quiver --skill ralph-iterate

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill automates one iteration of the Ralph loop to pick the next ready GitHub issue from a milestone, implement the change, and commit it, enabling autonomous batch processing of work.

Core Features & Use Cases

  • Selective iteration: automatically selects the next ready issue within a milestone.
  • Automated implementation: creates a feature branch, applies changes, runs validations, and commits.
  • Workflow automation: supports continuous processing of issues in large projects without human input.

Quick Start

Run a single Ralph loop iteration for a milestone by passing the milestone name as an argument. For example: ralph-iterate "Sprint-42"

Frequently Asked Questions about ralph-iterate

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

FAQPage Schema
How do I automate processing GitHub issues from a milestone queue?

You can automate GitHub issue processing by running a single loop iteration that selects the next ready issue from a specified milestone, creates a branch, applies changes, and commits. Pass the milestone name as an argument to start.

How does automated batch processing for GitHub issues work?

Automated batch processing works by running a loop that selects the next ready issue from a milestone, implements the change, and commits it. Each iteration handles one issue, allowing continuous processing of work queues without manual intervention.

Do I need the GitHub CLI and git installed to automate issue implementation?

Yes, both the GitHub CLI (gh) and git must be installed in your shell environment. These dependencies are required to fetch milestone issues, create feature branches, run validations, and push commits to your repository.

Can I use this approach to process issues continuously without human input?

Yes, this approach supports continuous processing of GitHub issues without human input. By running iterations sequentially, it selects ready issues from milestones, implements changes, and commits them to enable autonomous workflow automation.

What are the limitations of automating one iteration at a time for GitHub issues?

The main limitation is that each execution handles only a single issue from a milestone. You must trigger the iteration repeatedly to process an entire milestone queue, as it does not batch multiple issues within one run.