ralph loop
- Repo stars 2,914
- Author repo ralph-orchestrator
- Domain
- Engineering
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @mikeyobrien · no license declared
- Token usage
- Moderate
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Shell exec
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# Ralph Loop
Use this skill to operate Ralph loops from the outside.
## Use This Skill For
- Starting or continuing a Ralph run with the right `-c` and `-H` inputs
- Inspecting loop state, worktrees, logs, history, and diffs
- Resuming a hook-suspended loop
- Merging or discarding completed worktree loops
- Debugging unexpected loop behavior with current diagnostics files
## Workflow
1. Start with `ralph loops list` or `ralph loops list --json` to establish the
current state.
2. If the user wants execution, run `ralph run ...` with the right core config
and hats source.
3. If the loop is stuck or suspicious, inspect `logs`, `history`, and `diff`
before changing state.
4. If the loop is suspended, read `.ralph/suspend-state.json` and use
`ralph loops resume <id>`.
5. If a loop is queued or in `needs-review`, inspect the diff first, then use
`merge`, `process`, `retry`, or `discard` as appropriate.
6. Use diagnostics when you need detailed evidence about hats, events, tool
calls, parse errors, or performance.
## Guardrails
- Prefer the CLI over direct edits to `.ralph` state files.
- Treat tasks and memories as the canonical runtime systems; do not center
scratchpad as the primary state model.
- Inspect diffs before merging.
- Only remove lock or queue artifacts when the underlying process is confirmed
dead.
- Manual edits under `.ralph/` are last-resort recovery steps and should be
called out explicitly when used.
## Read These References When Needed
- For command recipes and operator flows: `references/commands.md`
- For diagnostics files and suspend-state details: `references/diagnostics.md`
Sections and files
Listed in source order.
sections -> Use This Skill For → Workflow → Guardrails → Read These References When Needed
terms -> Use this skill to operate Ralph loops from the outside. · 1. Start with ralph loops list or ralph loops list --json to establish the current state. · - Prefer the CLI over direct edits to .ralph state files.
files/cmd -> ralph loops list · ralph loops list --json · ralph run ... · logs · history · diff · .ralph/suspend-state.json · ralph loops resume <id>
body sha256 -> 2ec3c7863475
Use This Skill For
Starting or continuing a Ralph run with the right
-cand-Hinputs Inspecting loop state, worktrees, logs, history, and diffs Resuming a hook-suspended loop Merging or discarding completed worktree loops Debugging unexpected loop behavior with current diagnostics filesWorkflow
Start with
ralph loops listorralph loops list --jsonto establish the current state. If the user wants execution, runralph run ...with the right core config and hats source. If the loop is stuck or suspicious, inspectlogs,history, anddiffGuardrails
Prefer the CLI over direct edits to
.ralphstate files. Treat tasks and memories as the canonical runtime systems; do not center scratchpad as the primary state model. Inspect diffs before merging. Only remove lock or queue artifacts when the underlying process is confirmedRead These References When Needed
For command recipes and operator flows:
references/commands.mdFor diagnostics files and suspend-state details:references/diagnostics.md