Agent skill · Testing & QA

super-ralph-wiggum

Super Ralph Wiggum - autonomous iteration loops with templates, PRD support, progress tracking, and browser testing. This skill should be used when running Claude Code in autonomous loops for test coverage improvement, PRD-based feature development, documentation generation, dataset creation, lint fixing, code cleanup, or framework migrations. Combines the plugin's in-session loop mechanism with specialized templates and best practices from Geoffrey Huntley, Ryan Carson, and AI Hero.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill super-ralph-wiggum-tdimino-claude-code-minoan --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 12 KB
Bundled scripts: none
Path: skills/agent/super-ralph-wiggum-tdimino-claude-code-minoan/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Super Ralph Wiggum Autonomous iteration loops for Claude Code. Run the same prompt repeatedly until task completion, with context persisting through files and git history. ## The Ralph Philosophy > **The agent chooses the task, not you.** You define the end state. Ralph figures out how to get there. With multi-phase plans, a human writes a new prompt at the start of each phase. With Ralph, the agent picks what to work on next from your PRD. You describe the destination. Ralph navigates. ## The 11 Tips (Quick Reference) Based on [AI Hero's definitive guide](https://www.aihero.dev/tips-for-ai-coding-with-ralph-wiggum): | # | Tip | Key Insight | |---|-----|-------------| | 1 | Ralph Is A Loop | Same prompt, multiple iterations | | 2 | Start HITL, Then AFK | Learn → Trust → Let go | | 3 | Define The Scope | Explicit stop conditions prevent infinite loops | | 4 | Track Progress | progress.txt bridges context windows | | 5 | Use Feedback Loops | Types, tests, linting as guardrails | | 6 | Take Small Steps | One logical change per commit | | 7 | Prioritize Risky Tasks | Architecture first, quick wins last | | 8 | Define Software Quality | Tell Ralph what kind of repo this is | | 9 | Use

What's inside
Steps it walks through
  1. The Ralph Philosophy
  2. The 11 Tips (Quick Reference)
  3. Quick Start
  4. Available Templates
  5. Invocation Patterns
  6. Template Mode (Recommended)
  7. PRD Mode
  8. HITL Mode (Single Iteration)
  9. Custom Prompt
  10. The Two Modes: HITL vs AFK
  11. Explicitly Define Software Quality
  12. Code Quality Prompt
  13. The Repo Wins
  14. Task Prioritization Order
Ships with 1 file
  • metadata.json
Commands it runs
Generate external script
chmod +x run-ralph.sh
Run in background
rm .claude/ralph-loop.local.md
More from claude-skill-registry
All skills →
About this skill
What does the super-ralph-wiggum skill do?

Super Ralph Wiggum - autonomous iteration loops with templates, PRD support, progress tracking, and browser testing. This skill should be used when running Claude Code in autonomous loops for test coverage improvement, PRD-based feature development, documentation generation, dataset creation, lint fixing, code cleanup, or framework migrations. Combines the plugin's in-session loop mechanism with specialized templates and best practices from Geoffrey Huntley, Ryan Carson, and AI Hero.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill super-ralph-wiggum-tdimino-claude-code-minoan --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going