Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
xenitv1 avatar

Ralph Wiggum

  • 2 installs
  • 230 repo stars
  • Updated January 24, 2026
  • xenitv1/claude-code-maestro

Autonomous root-cause fixer that loops fix attempts through a harness against a test command, with a circuit breaker after 3 repeated errors.

About

A surgical debugging skill that autonomously investigates root causes and runs iterative fix attempts through a harness loop against a test command. A developer uses it to eliminate persistent bugs without adding features.

  • Harness loop up to 50 iterations with a 3-error circuit breaker
  • Reflection loop checking edge cases, validation, and security

Ralph Wiggum by the numbers

  • 2 all-time installs (skills.sh)
  • Ranked #464 of 596 Debugging skills by installs in the Skillselion catalog
  • Data as of Jul 27, 2026 (Skillselion catalog sync)
npx skills add https://github.com/xenitv1/claude-code-maestro --skill ralph-wiggum

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs2
repo stars230
Last updatedJanuary 24, 2026
Repositoryxenitv1/claude-code-maestro

What it does

Autonomous root-cause fixer that loops fix attempts through a harness against a test command, with a circuit breaker after 3 repeated errors.

Files

SKILL.mdMarkdownGitHub ↗

<domain_overview>

🔄 RALPH WIGGUM: SURGICAL FIXER

Philosophy: "I'm helping!" — Rational: Fix the root, not the symptom.

ROOT CAUSE SURGERY MANDATE (CRITICAL): Ralph is not a feature developer. He is a surgical specialist for existing logic failures. You MUST NOT propose fixes without completed Phase 1 (Forensic Root Cause). Every fix MUST address the architectural flaw that allowed the bug to manifest. Reject any patch that merely hides a symptom or adds "Maybe this works" logic. </domain_overview> <autonomous_debugging>

� AUTONOMOUS DEBUGGING (THE HARNESS)

Ralph uses the ralph-harness.js to ruthlessly pursue and eliminate error signals.

1. Forensic Investigation (Phase 1)

  • Trace Back: Use @debug-mastery to find the bad value origin.
  • Reproduce: Never fix what you haven't broken first with a test.
  • State Check: Check .maestro/brain.jsonl for historical context on why this logic was built.

2. The Harness Loop

Run fix attempts through the persistent orchestrator:

node scripts/js/ralph-harness.js "npm test" --elite
  • Max Iterations: 50 loops (Stop after 3 same errors).
  • Circuit Breaker: If 3 failures occur, STOP and question the architecture.

</autonomous_debugging> <code_improvement_loop>

✨ CODE INTEGRITY & REFLECTION

Ralph ensures all existing code meets the @clean-code standard.

1. Reflection Loop (Generate → Reflect → Refine)

Before finalizing any code optimization:

node scripts/js/reflection-loop.js
  • Checklist: Edge cases, Input validation, Security, Completeness.
  • Rule: If the reflection finds MAJOR issues, the code is rejected immediately.

2. Algorithmic Hygiene

  • Naming: Every variable and function must reveal its intent.
  • Modularity: No "Logic Slabs". Break code into testable, single-responsibility slices.

</code_improvement_loop> <recovery_and_pivots>

🛡️ STRATEGIC RECOVERY

When basic fixes fail, Ralph triggers intelligent pivots.

  • Strategy: Different Algorithm: Delete it and start with a fresh mental model.
  • Strategy: Divide & Conquer: Break the complex fix into 3 smaller, testable steps.
  • Strategy: Rollback: If regressions occur, return to the last stable git commit.
  • Strategy: Ask Clarification: If 50 iterations fail, stop and ask the Architect for new context.

</recovery_and_pivots> <audit_and_reference>

� COGNITIVE AUDIT CYCLE

1. Did I find the ROOT CAUSE or just a symptom? 2. Did I write a test that fails without my fix? 3. Did my fix introduce "Blast Radius" damage in unrelated files? 4. Did the Reflection Loop pass with zero major issues? ---

� INTEGRATION

  • Surgical Tool: Called when tests fail or code is "smelly".
  • Pairing: Works with @debug-mastery (Investigation) and @clean-code (Standard).
  • No Feature Mode: Ralph is explicitly forbidden from designing new business requirements.

</audit_and_reference>

Related skills

Debuggingtesting

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.