ralph-loop

Run self-correcting iterative loops to fix build errors and pass tests.

10|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/Lee-SiHyeon/oh-my-copilot --skill ralph-loop-lee-sihyeon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralph-loop
Source: https://github.com/Lee-SiHyeon/oh-my-copilot/tree/main/.github/skills/oh-my-copilot-ralph-loop
Command: npx skills add https://github.com/Lee-SiHyeon/oh-my-copilot --skill ralph-loop-lee-sihyeon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents you from getting stuck with partial or incorrect changes by repeatedly running a self-correcting loop until the work meets a defined completion condition.

Core Features & Use Cases

  • Self-correcting iterative workflow: Breaks a task into tracked TodoWrite steps, runs them, verifies results, and updates completion or failure per iteration.
  • Robust stopping criteria: Continues only while required checks fail and stops when the loop emits the required completion promise tag.
  • ULW critical verification mode: Adds an Oracle verification stage that rejects partial or unproven completion and restarts the loop in those cases.
  • Use case: Fixing a flaky or failing set of changes (for example, resolving TypeScript compile errors or getting tests to pass) by automatically cycling through analyze → implement → verify until success.

Quick Start

Ask it to run a full TypeScript error fix loop: "/ralph-loop 모든 TypeScript 컴파일 에러 수정".

Frequently Asked Questions about ralph-loop

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

FAQPage Schema
How do I automatically fix TypeScript compile errors until the build passes?

Automatically fix TypeScript compile errors by running a self-correcting iterative loop that analyzes the build state, applies step changes, and verifies outcomes until all errors are resolved. The loop continuously cycles implementation and verification until the build passes.

What is a self-correcting iterative debugging workflow for task verification?

A self-correcting iterative debugging workflow breaks a task into tracked TodoWrite steps, runs them, verifies results, and updates completion or failure per iteration. It stops only when a defined completion promise tag is emitted, ensuring convergence.

How do I set up an iterative testing loop to repeatedly clean lint issues?

Set up an iterative testing loop to clean lint issues by configuring bounded or customizable iterations that repeatedly analyze, implement fixes, and verify outcomes. The loop stops only when the expected completion signal is produced.

How does the loop handle partial or unproven task completion?

The loop handles partial or unproven task completion using an Oracle verification stage that rejects incomplete results and restarts the cycle. This ensures that only fully verified and proven completion stops the iterative execution.

When should I use a bounded iterative loop for Copilot CLI task verification?

Use a bounded iterative loop for Copilot CLI task verification when fixing flaky changes or resolving build errors that require convergence. It is ideal for scenarios needing repeated analyze, implement, and verify cycles until success is proven.

What are the limitations of relying on a completion promise tag to stop iterative debugging?

The limitation of relying on a completion promise tag is that iterative debugging strictly stops only when the expected signal is produced. If checks fail or completion remains unproven, the loop continues within bounded iterations until limits are reached.