ralph-cancel

Cancel an active Ralph Loop by removing its state file and reporting the stopped iteration.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a way to stop an active "Ralph Loop" process, preventing further iterations and resource consumption.

Core Features & Use Cases

  • Loop Termination: Safely cancels a running Ralph Loop by removing its state file.
  • Status Check: Verifies if a Ralph Loop is currently active before attempting cancellation.
  • Use Case: If a Ralph Loop is stuck in an infinite or undesirable cycle, you can use this Skill to halt its execution.

Quick Start

Cancel the active Ralph loop if it exists.

Frequently Asked Questions about ralph-cancel

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

FAQPage Schema
How do I cancel an active ralph loop that is stuck in an infinite cycle?

Cancelling an active ralph loop involves removing the state file `tmp/ralph-loop.local.md`. This skill safely deletes the file to halt the iterative process and reports the exact iteration number where execution stopped.

What happens to the iteration state when I stop a running ralph loop process?

When you stop a running ralph loop process, the state file `tmp/ralph-loop.local.md` is removed. The skill then reports the cancellation status alongside the specific iteration number at which the loop was terminated.

How do I check if a ralph loop is currently active before attempting to cancel it?

Checking if a ralph loop is active is handled automatically by verifying the existence of the state file `tmp/ralph-loop.local.md`. The skill performs this status check before attempting any cancellation actions.

Why does removing a state file stop a long-running iterative process?

Removing the state file stops the iterative process because the ralph loop relies on `tmp/ralph-loop.local.md` to maintain its execution context. Deleting this file interrupts the cycle, preventing further resource consumption.

Can I manage long-running ralph loops without leaving them stuck in an undesirable cycle?

Managing long-running ralph loops safely is possible by using this cancellation skill. It terminates undesirable cycles by deleting the state file, ensuring the iterative process halts and reports its final iteration number.