Run autonomous audit, resolve findings

Spawn QA agents iteratively to audit and fix findings until complete or max iterations reached.

prompt
→ Claude
--- description: Autonomous audit loop — router-managed iteration or standalone via Stop hook disable-model-invocation: true --- Run the ralph-loop audit. There are two modes: ## Mode 1: Router-managed iteration (multi-agent, default) The router manages the iteration loop by spawning and re-spawning subagents: 1. Read .claude/ralph/PROMPT.md (in the parent project C:\dev\projects ) for the audit instructions 2. Create a task for the audit 3. Spawn a QA agent to execute the audit pass 4. When the agent completes, read the audit state file ( agent-studio/.claude/context/runtime/ralph-audit-state.md ) 5. If open findings remain (agent output contains RALPH ITERATION COMPLETE ), spawn another QA agent iteration 6. Repeat until all findings are resolved ( RALPH AUDIT COMPLETE NO FINDINGS ) or max iterations (25) reached 7. Report final results The router remains free and never gets trapped. No stop hook is involved. ## Mode 2: Standalone Stop hook loop (single-session) For standalone use outside the multi-agent framework, launch via the shell scripts: bash # Unix/macOS .claude/ralph/ralph-audit.sh # Windows .claude\ralph\ralph-audit.bat These scripts set RALPH ACTI
claude-code

Source: oimiragieo

More automation loops

Launch autonomous Ralph backlog loop

Loop/ralphnew

Start a long-running autonomous agent loop for a change, monitor iterations until completion or stall, with configurable timeout and done criteria.

prompt
→ Claude
# Start Ralph Loop Start an autonomous Ralph loop for the given change-id and task. Arguments: <change-id> "<task description>" [--max N] [--done criteria] ## Instructions Start the Ralph loop and then monitor its progress until completion. ### Step 1: Start the loop bash set-loop start $ARGUMENTS ### Step 2: Monitor progress After starting, run the monitor command to track progress until the loop completes: bash set-loop monitor <change-id> --interval 30 This will output iteration updates and report the final status (done/stuck/stopped). ## Options - --max N - Maximum iterations (default: 10) - --done criteria - Done detection: tasks , openspec , or manual (default: tasks, auto-detects openspec) - --capacity-limit PCT - Stop if capacity exceeds threshold (default: 80%) - --stall-threshold N - Stall after N commit-less iterations (default: 2) - --iteration-timeout N - Per-iteration timeout in minutes (default: 45) - --permission-mode MODE - Claude permission mode: auto-accept , allowedTools , plan (default: config) - --label TEXT - Label for this loop instance (shown in banner and terminal title) - --force - Force start even w
automationhigh risk

Draft weekly release notes

Loop/schedulelooprepo

Every Friday at 2pm, draft release notes from merged PRs into releases/DRAFT.md and verify all links resolve.

prompt
→ Claude
/schedule every Friday at 2pm, draft release notes from the PRs merged since the last draft: group changes into features, fixes, and docs, write one plain-English line per change with the PR link, and save to releases/DRAFT.md. Draft only — a human edits and publishes; never post or send anywhere. Verify every PR link resolves and every merged PR since the last run is covered before saving. Stop after 1 pass per run.
automationlow risk

Implement a spec end-to-end

Loop/ralphnew

Run an autonomous agent loop to implement a complete spec file, iterating until all requirements are met and marked DONE.

prompt
→ Claude
--- description: Run the Ralph Wiggum loop for a spec (Claude Code) --- Use this command to run an autonomous Ralph loop for a spec: /ralph-loop:ralph-loop "Implement spec {spec-name} from specs/{spec-name}/spec.md. Complete ALL Completion Signal requirements. Output <promise>DONE</promise> when complete." --completion-promise "DONE" --max-iterations 30
automationmedium risk