| name | soulforge |
| description | Run high-signal autonomous coding loops with Soulforge (feature-dev/bugfix/review-loop) using strict worktree isolation, review gates, and scoped fix cycles. |
| metadata | {"openclaw":{"emoji":"🔥","requires":{"bins":"[Truncated]","env":"[Truncated]"}}} |
Soulforge (Effective Use Guide)
This is not a full engine reference. This is the operating playbook for getting high-quality autonomous coding outcomes with Soulforge.
Core Operating Model
Use Soulforge when you want: plan → implement → verify/test → PR → review/fix loops with minimal babysitting.
Preferred workflows:
feature-dev for end-to-end feature delivery
bugfix for diagnose-first, surgical fixes
review-loop for tightening an existing PR until clean
Golden Rules (Most Important)
- Never run from repo main checkout.
- Soulforge now enforces this guardrail.
- Always isolate work in worktrees.
- Default base:
<repo>/worktrees/
- Keep tasks tightly scoped.
- Specific issue, explicit acceptance criteria, explicit DO-NOT list.
- Treat review findings with discipline.
- FIX in-scope issues.
- Mark genuine extras as
SEPARATE.
- Use callback-exec only.
- HTTP callback mode is removed.