autonomous-loops

Orchestrates autonomous Claude Code loops from sequential pipelines to RFC-driven multi-agent DAGs.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/ZaxbyHub/ragappv3 --skill autonomous-loops-zaxbyhub
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: autonomous-loops
Source: https://github.com/ZaxbyHub/ragappv3/tree/main/.claude/skills/autonomous-loops
Command: npx skills add https://github.com/ZaxbyHub/ragappv3 --skill autonomous-loops-zaxbyhub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running Claude Code autonomously over long horizons is hard: context resets between invocations, parallel agents conflict, and naive loops waste tokens or stall on CI failures. This Skill provides proven patterns and architectures for building self-running development loops without human intervention. ## Core Features & Use Cases - Loop Pattern Spectrum: Six patterns from simple claude -p sequential pipelines and the NanoClaw REPL to infinite agent loops, Continuous Claude PR loops, and RFC-driven DAG orchestration (Ralphinho). - De-sloppify Pattern: A dedicated cleanup step after implementation that removes test slop and over-defensive code without constraining the implementer. - Merge Queue & Recovery: Dependency DAG execution with tiered quality pipelines, worktree isolation, and eviction-context recovery for merge conflicts. - Use Case: You need to add tests across a large codebase over several days. Use the Continuous Claude loop with --max-runs, a SHARED_TASK_NOTES.md context bridge, and automatic CI-failure repair to iterate and merge PRs unattended. ## Quick Start Ask the agent to set up a sequential claude -p pipeline that implements a feature with TDD, runs a de-sloppify cleanup pass, verifies the build, and commits.

Frequently Asked Questions about autonomous-loops

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run Claude Code autonomously in a loop?▼

Use the claude -p flag for non-interactive invocations chained in a shell script, or install Continuous Claude for a full loop that creates branches, opens PRs, waits on CI, and merges. Always set exit conditions like --max-runs, --max-cost, or --max-duration.

What is the difference between a sequential pipeline and a multi-agent DAG loop?▼

A sequential pipeline runs isolated claude -p steps in order and suits single focused changes. A DAG loop like Ralphinho decomposes an RFC into dependent work units, runs them in parallel worktrees with tiered quality pipelines, and lands them through a merge queue.

How do I preserve context between claude -p iterations?▼

Each claude -p call starts with a fresh context window, so bridge state through the filesystem. Continuous Claude uses a SHARED_TASK_NOTES.md file that the agent reads at the start of each iteration and updates at the end.

Why should I avoid negative instructions like 'do not write unnecessary tests'?▼

Negative instructions make the model hesitant about all tests and degrade quality unpredictably. Instead, let the implementer be thorough and add a separate de-sloppify step that removes language-feature tests, redundant type checks, and over-defensive error handling.

When should I not use the Ralphinho DAG orchestration pattern?▼

Skip it for single-file changes, quick iteration on one thing, or work without a written spec. Simpler patterns like a sequential pipeline, NanoClaw REPL, or Continuous Claude are better fits when there are no interdependent parallel work units.