ralph-loop
Skill2 starsChanged 42 days agoMITView on GitHub
Autonomous task runner that works through a PRD one task at a time. Launches ralph.sh in the background and monitors progress.
26 other projects use a version of this.
Adopted by
Most recently taken up by
- shawnclybor/clybor-claude-toolingtheir own version, first seen Nov 8, 2026
- ZhouYinLong-lab/Dog-Skillstheir own version, first seen Nov 8, 2026
- belumume/claude-skillstheir own version, first seen Nov 3, 2026
- burakkaygusuz/ralph-wiggumtheir own version, first seen Nov 1, 2026
- harness-mini/harness-minitheir own version, first seen Nov 1, 2026
- cornch-k/batontheir own version, first seen Nov 1, 2026
Used with
Projects with it also use to-issues and review.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.Other versions26 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 26
- mikeyobrien/ralph-orchestrator★ 3.2ksame name
- zrosenfield/sharepoint-ai-skills★ 96same name
- dannys-code-corner/incan★ 73same name
- yylo-dev/yylo★ 66same name
- regression-io/coder-config★ 47same name
- belumume/claude-skills★ 46same name
- xfstudio/skills★ 9same name
- mnzralee/claude-multi-agent-architecture★ 8same name
- shyamsridhar123/kevin-copilot★ 7same name
- ZhouYinLong-lab/Dog-Skills★ 7same name
16 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository16 other files it gives its agents.
- audit-backendSkill
- audit-frontendSkill
- audit-securitySkill
- ralph-planSkill
- againSkill
- elimSkill
- huhSkill
- ughSkill
- code-audit-jevSkill
- jev-email-analysisSkill
- prompt-injection-evalSkill
- resume-mirror-evalSkill
- run-jevSkill
- traffic-triage-evalSkill
- built-withSkill
- github-remediate-vulnsSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
19 rules. 0 are common, 9 are distinctive, and 10 are very specific to this project.
0
Common
Most of the 22 edited versions we read keep these.
9
Distinctive
This author's own choices. Worth a look.
10
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 20
If a name was provided (e.g., /ralph-loop claude-guide), verify tasks/ralph/{name}/prd.md exists.
- Very specific: line 21
If no name was provided, list directories under tasks/ralph/ and:
- Distinctive: line 22
If there's exactly one, use it
- Distinctive: line 23
If there are multiple, ask the user which one to run
- Very specific: line 24
If there are none, tell the user to run /ralph-plan first and stop
- Distinctive: line 25
If the PRD file doesn't exist, tell the user and stop.
- Very specific: line 31
Read tasks/ralph/{name}/prd.md and count initial - [ ] and - [x] tasks.
- Very specific: line 33
Run ~/.claude/skills/ralph-loop/ralph.sh {name} {max_iterations} via the Bash tool with run_in_background: true.
- Very specific: line 41
Read tasks/ralph/{name}/prd.md — count - [ ] (remaining) and - [x] (completed).
- Very specific: line 42
Check background task status via TaskOutput with block: false.
- Distinctive: line 46
If nothing changed, do NOT print anything — silently continue polling.
- Distinctive: line 47
If the background task is still running, loop back to step 1.
- Distinctive: line 48
If the background task has finished, proceed to the Final Summary.
- Distinctive: line 52
When the background task completes (or errors):
- Very specific: line 54
Read tasks/ralph/{name}/prd.md one final time — count completed and remaining.
- Very specific: line 55
Read the background task output via TaskOutput with block: false to check for errors.
- Very specific: line 63
If there are remaining - [ ] tasks, mention: "Run /ralph-loop {name} again to continue."
- Distinctive: line 64
If the background task exited with an error, include the last 10 lines of output.
- Distinctive: line 67
Never commit: Do not run git add, git commit, or any git commands.
“Common” is measured: kept by at least 6 in 10 of the 22 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
You are Ralph's monitor — you launch the autonomous task runner in the background and report progress.
Setup
The user invoked /ralph-loop with optional arguments: the plan name and/or a max-iterations number.
Examples: /ralph-loop, /ralph-loop claude-guide, /ralph-loop claude-guide 50, /ralph-loop 50
- Parse arguments: a numeric argument sets
max_iterations(default: 10). A non-numeric argument is the plan name. - If a name was provided (e.g.,
/ralph-loop claude-guide), verifytasks/ralph/{name}/prd.mdexists. - If no name was provided, list directories under
tasks/ralph/and:- If there's exactly one, use it
- If there are multiple, ask the user which one to run
- If there are none, tell the user to run
/ralph-planfirst and stop
- If the PRD file doesn't exist, tell the user and stop.
Launch
Once you have a valid plan:
- Read
tasks/ralph/{name}/prd.mdand count initial- [ ]and- [x]tasks. Report: "Launching Ralph: {name} — {completed}/{total} tasks complete. Running up to {max_iterations} iterations." - Run
~/.claude/skills/ralph-loop/ralph.sh {name} {max_iterations}via the Bash tool withrun_in_background: true. Save the task ID. - Tell the user: "ralph.sh is running in the background. I'll report when tasks complete. You can continue working."
Monitor
Poll every 60 seconds until the background task finishes:
- Sleep 60 seconds (use Bash:
sleep 60). - Read
tasks/ralph/{name}/prd.md— count- [ ](remaining) and- [x](completed). - Check background task status via
TaskOutputwithblock: false. - Only print a status update if the completed count changed since the last check. Format:
"{completed}/{total} tasks complete."
Then read the last 30 lines of
tasks/ralph/{name}/progress.mdand extract the most recent## Iterationentry's**Completed**line. Append it: "Latest: {task description}" - If nothing changed, do NOT print anything — silently continue polling.
- If the background task is still running, loop back to step 1.
- If the background task has finished, proceed to the Final Summary.
Final Summary
When the background task completes (or errors):
- Read
tasks/ralph/{name}/prd.mdone final time — count completed and remaining. - Read the background task output via
TaskOutputwithblock: falseto check for errors. - Report:
Ralph complete: {name} - Tasks completed: {completed}/{total} - Remaining: {remaining} - See tasks/ralph/{name}/progress.md for full details - If there are remaining
- [ ]tasks, mention: "Run/ralph-loop {name}again to continue." - If the background task exited with an error, include the last 10 lines of output.
Rules
- Never commit: Do not run git add, git commit, or any git commands.
- Output location: Inherited from ralph.sh — files go into the plan directory unless PRD says otherwise.
- One task at a time: Inherited from ralph.sh — each iteration handles one task in a fresh claude session.
- Do not modify the PRD or progress files — ralph.sh handles that.
- Do not run ralph.sh inline — always use
run_in_background: true.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

