ralph-loop

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Chinese

Use this skill to operate Ralph loops from the outside.

使用此技能从外部操作Ralph循环。

Start with
```
ralph loops list
```
or
```
ralph loops list --json
```
to establish the current state.
If the user wants execution, run
```
ralph run ...
```
with the right core config and hats source.
If the loop is stuck or suspicious, inspect
```
logs
```
,
```
history
```
, and
```
diff
```
before changing state.

If the loop is suspended, read

.ralph/suspend-state.json

and use

ralph loops resume <id>

If a loop is queued or in
```
needs-review
```
, inspect the diff first, then use
```
merge
```
,
```
process
```
,
```
retry
```
, or
```
discard
```
as appropriate.
Use diagnostics when you need detailed evidence about hats, events, tool calls, parse errors, or performance.

如果循环已暂停，读取

.ralph/suspend-state.json

并使用

ralph loops resume <id>

恢复。

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.

For command recipes and operator flows:
```
references/commands.md
```
For diagnostics files and suspend-state details:
```
references/diagnostics.md
```