loop-engineering

From public sources

Practical patterns, starters & CLI tools for loop engineering with AI coding agents. Design systems that prompt and orchestrate agents (inspired by Addy Osmani and Boris Cherny). Includes loop-audit, loop-init, loop-cost.

AI toolCategory: AI AgentsOpen sourcedata checked Oct 16, 2026

Overview

  • agentic-ai
  • ai-agents
  • ai-coding
  • anthropic
  • automation
  • claude
  • claude-code
  • codex
  • coding-agents
  • devops-automation
  • devtools
  • github-actions

Installation

Commands are shown, never run by the marketplace. Check them against the official documentation.

Compatibility

Unknown means no evidence was found — not that the product is incompatible.
PlatformStatusArchitectureEvidenceConfidence
WindowsUnknown———
macOSUnknown———
LinuxUnknown———
Web browserUnknown———
Server / self-hostedUnknown———
Container (OCI)Unknown———

Releases

checked Oct 30, 2026
v1.6.0LatestJul 20, 2026Official source ↗

Files in 1.6.0

This release has no attached files.

Release history

Quality profile

algorithm quality-v1.0 · assessed Oct 16, 2026
Quality Score93
Risk Score0
Confidence 1.00
Quality Score and Risk Score are different measures. A high score does not guarantee safety.

Score components

Maintenance · 2020
last activity 1 days ago
Documentation · 1515
README 7057 chars, description present
Ready to use · 1515
install instructions: yes; releases: yes
Metadata · 1010
4/4 of description, homepage, license, topics
Releases · 108
2 release(s), latest 87 days ago
Category confidence · 105
classifier confidence 0.5
Adoption · 1010
11552 stars (log-dampened, 10k = max)
License clarity · 55
SPDX MIT
Community · 55
issues enabled, 1572 forks

License

MIT
Known licensefrom the repository host

This is the catalog policy status, not legal advice.

Sources

github.com/cobusgreyling/loop-engineeringPrimary★ 11,552 starslast activity Oct 15, 2026Primary repository · Confidence 1.00

Reviews

Sign in to write a review

No reviews yet.

Alternatives

README

From cobusgreyling/loop-engineering · license MIT · fetched Oct 30, 2026

Loop Engineering

Stop prompting. Design the loop. Get a score.

npx @cobusgreyling/loop init . --pattern daily-triage --tool claude
npx @cobusgreyling/loop doctor .

--tool defaults to claude if you omit it. Swap for grok, codex, or opencode. Week one is report-only.

You design a system that discovers work, hands it to agents, verifies results, and persists state — instead of typing the next prompt yourself.

New here? Quickstart · Refactor a project · Thin GitHub Action loop (no STATE.md required)

What do you want to do?

This is a pattern library for operating agents around a codebase. It is not a “rewrite the module” button.

I want to…Start here
Keep the repo healthy (issues, CI, deps)Quickstart → daily-triage
Land and babysit PRsPR Babysitter
Run a loop in GitHub Actions with almost no filesThin loop
Ship a feature or refactor (todos → small PRs)Refactor / change path

Full jobs table: docs/jobs.md.

Patterns

PatternCadenceWeek 1Cost
Daily Triage1d–2hL1 reportLow
Thin loopevent + 1dL1 snapshotVery low
PR Babysitter5–15mL1 watchHigh
CI Sweeper5–15mL2 cautiousVery high
Dependency Sweeper6h–1dL2 patch-onlyMedium
Changelog Drafter1d or tagL1 draftLow
Post-Merge Cleanup1d–6hL1 off-peakLow
Issue Triage2h–1dL1 propose-onlyLow

Interactive picker: showcase. Index: patterns/registry.yaml.

Getting started

npx @cobusgreyling/loop init . --pattern daily-triage --tool claude
npx @cobusgreyling/loop doctor .
npx @cobusgreyling/loop cost --pattern daily-triage --level L1

Empty repo → first STATE.md walkthrough: scripts/empty-to-state-demo.sh.

Roll out L1 report → L2 assisted → L3 unattended only after the verifier has been right for a week. See loop-design-checklist.

Loop Ready now weights recent runs harder than files on disk. A 30-day-old STATE.md is not L3.

Examples by tool

Claude Code (including the plugin) · Grok · Codex · OpenClaw · Opencode · GitHub Actions

Operating & safety

Failure modes · Anti-patterns · Safety · Operating loops · Stories (wins and failures)

Loop engineering amplifies judgment. Token costs can explode. Unattended loops make unattended mistakes. Read what the loop ships.

Help wanted

Docs and small PRs: first response within 48 hours.

See CONTRIBUTING.md.

Unified front door: npx @cobusgreyling/loop (init · doctor · status · audit · cost). Older packages (loop-init, loop-audit, …) stay supported.

Companions exist for later: memory-engineering, harness-foundry, outerloop, fleet-engineering, goal-engineering. Do not add them until a loop has actually run.

Sources

License

MIT

Open the repository ↗