mcpField
I
install-loop

install-loop

github.com/cobusgreylingAgent workflows11.7k93 installsUpdated today
Repository

About install-loop

install-loop guides an Agent through setting up a report-only engineering loop in a repository with one CLI, then checking its health and next steps. It also covers pattern and tool selection, cost checks, and first-week safety limits.

Key features

  1. 01Detect existing loop configuration
  2. 02Choose a loop pattern by pain point
  3. 03Select Claude, Grok, Codex, or OpenCode
  4. 04Initialize and inspect loop status
  5. 05Check costs before frequent runs
  6. 06Keep the first week report-only

Use cases

  1. 01Set up daily triage for a repository
  2. 02Choose a loop for CI failures or stalled PRs
  3. 03Inspect an existing setup and identify next steps

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/cobusgreyling/loop-engineering --skill install-loop

After installing, type/install-loopin Claude Code to confirm it loaded.

Details

From the project README

Install Loop Engineering

Goal

Leave the repo with a scaffolded report-only loop, a Loop Ready score, and clear next actions — using the single CLI:

npx @cobusgreyling/loop

Do not deprecate or remove existing loop-init / loop-audit usages you find; both doors stay valid. Prefer loop for new work.

Steps

  1. Detect context

    • If LOOP.md or STATE.md already exists, run doctor only (skip init unless human asks to re-scaffold): 
      npx @cobusgreyling/loop doctor . --json
npx @cobusgreyling/loop status .
    • Otherwise continue.

  2. Pick pattern (default: daily-triage)

    PainPattern
    Morning chaos / unclear prioritiesdaily-triage
    PRs stallingpr-babysitter
    CI red / flakesci-sweeper
    CVE / Dependabot noisedependency-sweeper
    Post-merge TODOspost-merge-cleanup
    Stale release noteschangelog-drafter
    Noisy issuesissue-triage
    One GitHub Action, almost no filesthin-loop

  3. Pick tool — claude | grok | codex | opencode (default claude).

  4. Scaffold

    npx @cobusgreyling/loop init . --pattern <pattern> --tool <tool>

    Optional harness (only if human wants Foundry): add --with-foundry.

  5. Doctor

    npx @cobusgreyling/loop doctor .
    • Exit 0 = healthy · 1 = warnings · 2 = blocked
    • Follow the top 3 printed actions; do not invent extra architecture.

  6. Cost check before high-cadence schedules:

    npx @cobusgreyling/loop cost -p <pattern> -l L1 -c 1d

  7. Week-one rule

    • Report only. No auto-fix, no auto-merge.
    • Tell the human the first /loop or scheduler command from init output.
    • Suggest badge only when score is strong: npx @cobusgreyling/loop badge .

Compatibility

These remain fully supported (do not rewrite existing docs/scripts unless asked):

npx @cobusgreyling/loop-init .
npx @cobusgreyling/loop-audit . --suggest

Stop conditions

  • Stop after doctor + first-run instructions unless the human asks for L2+.
  • Never expand into fleet/memory/foundry unless score ≥ 80 and human opts in.

Comments

Markdown supported