Skip to content

xpepper/pr-review-agent-skill / ralph-wiggum-loop

ralph-wiggum-loop

Verified

Use when context window exhaustion is a concern or when addressing a large volume of PR comments — spawns a fresh agent session per comment via an external shell loop. For an in-session approach, use pr-review-loop or copilot-review-loop instead.

Ralph Wiggum Loop

Overview

The Ralph Wiggum pattern: an external shell loop that spawns a fresh agent session per PR comment. Each invocation reads a plan file, does exactly one unit of work (triage or fix), then exits. The shell loop handles repetition.

This avoids context window exhaustion and works with any agent.

How to invoke

This skill is not invoked via chat. Instead, you run a shell loop in your terminal — the loop pipes CODE_REVIEW_PLAN.md to a fresh agent session for each iteration:

# Claude
while [ ! -f PR_REVIEW_DONE ]; do
  cat CODE_REVIEW_PLAN.md | claude -p --dangerously-skip-permissions
done

# Codex
while [ ! -f PR_REVIEW_DONE ]; do
  cat CODE_REVIEW_PLAN.md | codex exec --yolo -
done

See Setup below to get CODE_REVIEW_PLAN.md into your project.

Setup (once per PR)

  1. Copy CODE_REVIEW_PLAN.md from this skill to your project root:

    # Project-local install (default — installed without --global):
    cp .agents/skills/ralph-wiggum-loop/CODE_REVIEW_PLAN.md .
    
    # Global install (installed with --global):
    cp ~/.claude/skills/ralph-wiggum-loop/CODE_REVIEW_PLAN.md .
    

    The path depends on how the skill was installed. Check .agents/skills/ first (project-local); if not found, use your global skills directory.

  2. Optionally add both files to .gitignore:

    CODE_REVIEW_PLAN.md
    PR_COMMENTS_PLAN.md
    PR_REVIEW_DONE
    .pr-review/
    
  3. Start the loop:

    Claude:

    while [ ! -f PR_REVIEW_DONE ]; do
      cat CODE_REVIEW_PLAN.md | claude -p --dangerously-skip-permissions
    done
    

    Codex:

    while [ ! -f PR_REVIEW_DONE ]; do
      cat CODE_REVIEW_PLAN.md | codex exec --yolo -
    done
    

    Any agent that accepts stdin:

    while [ ! -f PR_REVIEW_DONE ]; do
      cat CODE_REVIEW_PLAN.md | <agent-command>
    done
    

How it works

IterationPR_COMMENTS_PLAN.md exists?What the agent does
1stNoFetches all PR comments, triages them, writes the file
2nd–NYesFixes the topmost unresolved comment, marks it done
FinalYes, all resolvedWrites PR_REVIEW_DONE, loop terminates

Each session is minimal: one triage pass or one comment fix.

State files (in project root)

  • CODE_REVIEW_PLAN.md — the instruction file (static, copied once)
  • PR_COMMENTS_PLAN.md — triage + progress state (generated, updated each run)
  • PR_REVIEW_DONE — written by the agent when all comments are addressed; stops the loop
  • .pr-review/plan-<id>.md — per-comment plan for non-trivial fixes (deleted after resolution)

Cleanup

rm -f CODE_REVIEW_PLAN.md PR_COMMENTS_PLAN.md PR_REVIEW_DONE
rm -rf .pr-review/

Do Not

  • Run the loop with --dangerously-skip-permissions on a repository you do not fully trust
  • Let the loop run unattended past the first few iterations without reviewing what the agent committed
  • Bundle all PR feedback into one large commit (each agent session commits at most one fix)
  • Delete PR_COMMENTS_PLAN.md while the loop is running — this is the shared state file
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 469kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 321kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 321kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 321kUpdated Claude CodeCodexVerifiedInstall