← ClaudeAtlas

looplisted

Autonomously iterate build→verify→review until every gate is green or a guardrail halts. Drives the specclaw-loop controller — evaluate gates, reflect, fix the smallest diff, re-verify the whole change, and repeat. Use when asked to loop, iterate until done, or keep fixing until tests pass / verify passes / review is clean. Default-on around /specclaw:build and /specclaw:verify.
chan4lk/specclaw · ★ 12 · AI & Automation · score 64
Install: claude install-skill chan4lk/specclaw
# specclaw loop **First, run** `specclaw-ensure-init .specclaw` — idempotently creates `.specclaw/` if it doesn't exist (silent if already initialized; auto-inits using the current directory's basename as the project name). Autonomously drive the change to all-green. The **controller** (`specclaw-loop`) owns every mechanical decision — gate evaluation, signatures, caps, no-progress / regression / oscillation detection, the reward-hack guard, and state/log persistence. This skill only orchestrates the LLM steps: reflect, spawn a fix agent, commit. Follow the controller's JSON verbatim — do not second-guess a `halt`. ## Step 0 — Validate prerequisites The loop presumes `/specclaw:plan` and at least one `/specclaw:build` pass have already run — it remediates an existing implementation, it does not create one. Confirm the change is built: ```bash specclaw-validate-change .specclaw <change> verify ``` If it fails (tasks not all complete / no build), tell the user to run `/specclaw:build` first and stop. Read `loop.enabled` from `.specclaw/config.yaml`: ```bash grep -A1 '^loop:' .specclaw/config.yaml ``` If `loop.enabled` is `false`, tell the user the autonomous loop is disabled and to run `/specclaw:build` and `/specclaw:verify` normally, then **stop**. Otherwise continue. ## Step 1 — Init ```bash specclaw-loop init .specclaw <change> ``` Seeds `loop-state.json` and `loop-log.md` (idempotent — never clobbers an existing state or log). Send a **loop started** notificati