ralph-loop

Run tests, coverage, type-check, and lint gates until all pass or escalate.

19|3|Updated Jan 13, 2026
One-click install
npx skills add https://github.com/changoo89/claude-pilot --skill ralph-loop-changoo89
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralph-loop
Source: https://github.com/changoo89/claude-pilot/tree/main/.claude/skills/ralph-loop
Command: npx skills add https://github.com/changoo89/claude-pilot --skill ralph-loop-changoo89

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After the first code change, developers often face failing tests, low coverage, and lint/type-check issues that stall progress. This skill automates the Ralph Loop, orchestrating deterministic iterations until all quality gates pass or escalation is required.

Core Features & Use Cases

  • Autonomous post-change iteration: runs tests, checks coverage, type-check, and lint until all gates are green or the maximum iterations are reached.
  • Escalation for blockers: when progress stalls, it triggers escalation to a GPT Architect or team lead to unblock the workflow.
  • Progress tracking and governance: maintains state across iterations, supports early escalation with the --early flag, and completes when tasks pass.
  • Adaptable workflow: integrates with project pipelines and pilot documents; supports both standard and architecture-driven escalation paths.

Quick Start

After making your first code change, initiate the Ralph Loop to automatically iterate until all quality gates pass or escalate when blocked.

Frequently Asked Questions about ralph-loop

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

FAQPage Schema
How do I automate test coverage, lint, and type-check fixes after making a code change?

Automate post-change quality verification by running a deterministic loop that iterates through tests, coverage, type-check, and lint gates until all pass. It applies fixes automatically and tracks iterations to ensure all quality gates are green.

What is the best way to handle failing tests and low coverage blocking my development progress?

Handle failing tests and low coverage by initiating an autonomous post-change iteration loop. It runs verification checks, applies fixes, and escalates to a GPT Architect or team lead when progress stalls, unblocking your workflow.

Can I escalate architecture issues early while running post-change quality verification?

Yes, you can escalate architecture issues early using the --early flag. This triggers an architecture-driven escalation path to a GPT Architect when progress stalls, ensuring blockers are addressed before reaching maximum iterations.

Does the autonomous quality verification loop maintain state across multiple iterations?

Yes, the autonomous verification loop maintains state across iterations to provide progress tracking and governance. It ensures deterministic execution by tracking each iteration and completing only when all tasks pass or escalation occurs.

What happens when the automated quality verification loop reaches maximum iterations without passing?

When maximum iterations are reached without passing all gates, the loop triggers an escalation. It escalates the unresolved blockers to a GPT Architect or team lead to analyze the stalled progress and unblock the workflow.