install-loop

Scaffolds report-only agent loops in repositories via the @cobusgreyling/loop CLI.

10.8k|1.5k|Updated Jun 9, 2026
One-click install
npx skills add https://github.com/cobusgreyling/loop-engineering --skill install-loop
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: install-loop
Source: https://github.com/cobusgreyling/loop-engineering/tree/main/skills/install-loop
Command: npx skills add https://github.com/cobusgreyling/loop-engineering --skill install-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Setting up an agent-operating loop around a codebase involves choosing a pattern, picking an agent tool, scaffolding files, and validating health — doing this manually is error-prone. This Skill walks through the entire installation using the single unified npx @cobusgreyling/loop CLI, leaving the repo with a report-only loop, a Loop Ready score, and clear next actions.

Core Features & Use Cases

  • Context detection: Checks for existing LOOP.md or STATE.md and runs doctor/status only when a loop already exists, avoiding accidental re-scaffolding.
  • Pattern and tool selection: Maps common pains (morning chaos, stalling PRs, red CI, Dependabot noise) to patterns like daily-triage, pr-babysitter, ci-sweeper, and thin-loop, across claude, grok, codex, or opencode.
  • Safe week-one defaults: Enforces report-only operation — no auto-fix or auto-merge — and gates expansion (fleet, memory, Foundry) behind a doctor score of 80+ with explicit human opt-in.
  • Use Case: A maintainer wants CI triage automated. The Skill detects no existing loop, scaffolds ci-sweeper for claude, runs doctor, checks cost with loop cost, and hands back the first /loop command.

Quick Start

Install Loop Engineering into this repository using the daily-triage pattern with the claude tool, then run doctor and show me the score and next actions.

Frequently Asked Questions about install-loop

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

FAQPage Schema
How do I install Loop Engineering into my repository?▼

Run npx @cobusgreyling/loop init . --pattern daily-triage --tool claude to scaffold the loop, then npx @cobusgreyling/loop doctor . to verify health. The tool flag defaults to claude and supports grok, codex, and opencode.

Which loop pattern should I choose for my project?▼

Match the pattern to your pain: daily-triage for unclear priorities, pr-babysitter for stalling PRs, ci-sweeper for red CI, dependency-sweeper for CVE noise, and thin-loop for a minimal single GitHub Action setup.

What happens if LOOP.md or STATE.md already exists?▼

The Skill skips scaffolding and only runs npx @cobusgreyling/loop doctor . --json and loop status to assess the existing loop. Re-scaffolding only happens if the human explicitly asks.

Can the loop auto-merge PRs or apply fixes automatically?▼

No. Week-one operation is strictly report-only with no auto-fix or auto-merge. Auto-merge or unattended fixes are never enabled unless the human explicitly asks and doctor reports a healthy state.

What do the loop doctor exit codes mean?▼

Exit code 0 means healthy, 1 means warnings, and 2 means blocked. Follow the top three printed actions from doctor output rather than inventing additional architecture.

When can I expand to fleet, memory, or Foundry features?▼

Expansion is only allowed when the doctor score is 80 or higher and the human explicitly opts in. The optional Foundry harness is added at init time with the --with-foundry flag.