git404hub

what is loop-engineer fr?

fltman/loop-engineer — explained in plain English

Analysis updated 2026-05-18

33ShellAudience · developerComplexity · 3/5LicenseSetup · moderate

tl;dr

A Claude Code skill and subagent that scaffolds automated agentic loops with built-in safety limits like iteration caps, spending caps, and human checkpoints.

vibe map

mindmap
  root((repo))
    What it does
      Scaffolds agent loops
      Enforces guardrails
      Five loop patterns
    Tech stack
      Shell scripts
      Claude Code
    Guardrails
      Verifiable exit
      Iteration cap
      Budget cap
      Human checkpoint
    Audience
      Developers using Claude Code

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

what do people make with this?

VIBE 1

Scaffold a guardrailed loop that runs Claude Code until a test suite passes.

VIBE 2

Design a multi-step agent loop interactively using the included loop-architect subagent.

VIBE 3

Audit an existing agent loop against the project's five safety guardrails.

VIBE 4

Set up a fan-out orchestrator loop for subtasks that cannot be planned in advance.

what's the stack?

ShellClaude Code

how it stacks up fr

fltman/loop-engineerrejectall/expertteam-codexvarshanam31/weather-app
Stars333333
LanguageShellShellShell
Setup difficultymoderateeasyeasy
Complexity3/52/51/5
Audiencedeveloperdevelopergeneral

Figures from each repo's GitHub metadata at analysis time.

how do i run it?

Difficulty · moderate time til it works · 30min

Requires Claude Code installed and copying the skill files into a project's or global configuration folder.

Use freely for any purpose, including commercial use, as long as you keep the copyright notice.

in plain english

This project is a skill and subagent for Claude Code, Anthropic's coding assistant tool, that helps a developer set up what the README calls agentic loops: automated cycles where an AI agent runs repeatedly against a task instead of being prompted once by a human. Rather than inventing new loop tools, this project scaffolds and adds safety limits around loop features that already exist in Claude Code, such as running it headlessly, its built in loop and goal commands, tasks, and scheduled cloud routines. The README describes five loop patterns: a simple loop that checks one pass or fail condition, an evaluator-optimizer pattern where a separate step judges the output of a generating step, a meta loop that improves the prompt another loop uses, an orchestrator that fans work out to multiple workers when the subtasks cannot be predicted ahead of time, and a scheduled loop that runs on a timer. Each pattern has a runnable shell script template. The README states these patterns can be nested, such as an orchestrator that spawns evaluator-optimizer loops inside it. The central rule stated in the README is that a loop must have a verifiable, binary exit condition, since a vague goal like improving user experience has no clear pass or fail state and can run indefinitely while accumulating cost. It cites an example of a four-agent loop running eleven days and costing about forty seven thousand dollars because it lacked this check. Every scaffold the project produces is said to enforce five safeguards: a verifiable exit condition checked each run, a hard maximum iteration count set in code, a spending cap enforced in code rather than only alerted on, running inside a sandboxed environment such as a separate branch rather than directly on the main branch, and a required human checkpoint before any irreversible action like a deployment or a message being sent. To use it, someone copies the skill and agent files into a project's or their global Claude Code configuration folder. It can then be triggered by describing a loop in plain language, designed step by step with an included interactive subagent, or run directly through shell scripts with environment variables setting the exit check, task prompt, iteration cap, and budget. The README credits Anthropic's published research on agent architecture patterns as a source, and states community-created patterns are labeled as such rather than presented as official guidance. The project is released under the MIT license.

prompts (copy fr)

prompt 1
Set up a loop that runs until my tests pass, with a max of 10 iterations and a $5 budget cap.
prompt 2
Explain the difference between the headless loop and evaluator-optimizer patterns in this project.
prompt 3
Audit this loop script against the five-point guardrail checklist from loop-engineer.
prompt 4
Walk me through installing loop-engineer's skill and agent into my project's Claude Code config.
prompt 5
Help me design a meta loop that refines the prompt another loop uses, based on this project's pattern.

Frequently asked questions

what is loop-engineer fr?

A Claude Code skill and subagent that scaffolds automated agentic loops with built-in safety limits like iteration caps, spending caps, and human checkpoints.

What language is loop-engineer written in?

Mainly Shell. The stack also includes Shell, Claude Code.

What license does loop-engineer use?

Use freely for any purpose, including commercial use, as long as you keep the copyright notice.

How hard is loop-engineer to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is loop-engineer for?

Mainly developer.

peek the repo → explain another one

This repo across BitVibe Labs

double-check against the repo, no cap.