You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 5b152f8
Browse filesBrowse the repository at this point in the historyBrowse files
Cobus Greyling
authored and
Cobus Greyling
committed
fix: publish umbrella CLI as @cobusgreyling/loop-cli 0.1.1
npm accepted 0.1.0 under @cobusgreyling/loop but the package never
appeared on the registry, and the bin name was stripped. Rename to
loop-cli (aligned with loop-audit/loop-init), fix bin to dist/cli.js,
and bump to 0.1.1 for a clean public release.
# Same as before (still fully supported — forks need not change)
44
44
npx @cobusgreyling/loop-init .
45
45
# Optional: also scaffold a versioned harness (harness-foundry)
46
-
npx @cobusgreyling/loop init . --with-foundry
46
+
npx @cobusgreyling/loop-cli init . --with-foundry
47
47
```
48
48
49
49
`loop init` (or `loop-init`) scaffolds skills, state, and budget files, then prints your **Loop Ready** score and first loop command. `loop doctor` combines audit + sync + file checks into top-3 next actions. Swap `--tool` for `claude`, `codex`, or `opencode`. Use `--with-foundry` when you want the loop as a composable runtime stack. See [docs/cli-front-door.md](docs/cli-front-door.md).
@@ -88,17 +88,17 @@ For developers using Grok, Claude Code, Codex, Cursor, and other AI coding agent
88
88
| Start here | Description |
89
89
|------------|-------------|
90
90
|[Quickstart (5 min)](docs/QUICKSTART.md)|`loop init` → `loop doctor` → first loop — **start here if you just landed**|
91
-
|[CLI front door](docs/cli-front-door.md)| Unified `@cobusgreyling/loop` — old packages stay open |
91
+
|[CLI front door](docs/cli-front-door.md)| Unified `@cobusgreyling/loop-cli` — old packages stay open |
92
92
|[Loop Engineering essay](https://cobusgreyling.substack.com/p/loop-engineering)| The concept, primitives, and Grok mapping — read for the why |
93
93
|[Pattern Picker](docs/pattern-picker.md)| Which loop to run first — **start here if unsure**|
94
94
|[Primitives Matrix](docs/primitives-matrix.md)| Cross-tool loop primitive mapping — bookmark this |
@@ -68,7 +68,7 @@ Adjust `--pattern`, `--level` (L1 → L2 → L3), and `--cadence` to match what
68
68
When a loop starts fixing code unattended, wire a **circuit breaker** so it escalates instead of retrying the same failure forever. `loop-init` scaffolds `loop-ledger.json` and a `loop-guard` skill for fix-capable patterns; check the ledger before each retry:
# same as: npx @cobusgreyling/loop-context --check --ledger loop-ledger.json
73
73
```
74
74
@@ -78,21 +78,21 @@ Exit `0` = continue · `2` = escalate to a human. The breaker trips on max itera
78
78
79
79
```bash
80
80
# Prefer doctor for day-to-day (includes audit + sync)
81
-
npx @cobusgreyling/loop doctor .
81
+
npx @cobusgreyling/loop-cli doctor .
82
82
# Or audit alone:
83
-
npx @cobusgreyling/loop audit . --suggest
83
+
npx @cobusgreyling/loop-cli audit . --suggest
84
84
```
85
85
86
86
Scores 0–100 with concrete next steps. Re-run after each improvement. Paste a badge when you're proud of the score:
87
87
88
88
```bash
89
-
npx @cobusgreyling/loop badge .
89
+
npx @cobusgreyling/loop-cli badge .
90
90
```
91
91
92
92
When the score is **≥ 80**, audit (and `loop init`) nudge you to version the loop as a [harness-foundry](https://github.com/cobusgreyling/harness-foundry) stack — declarative runtime, traces, outerloop emit:
93
93
94
94
```bash
95
-
npx @cobusgreyling/loop init . --with-foundry
95
+
npx @cobusgreyling/loop-cli init . --with-foundry
96
96
npx @cobusgreyling/harness-foundry validate
97
97
npx @cobusgreyling/harness-foundry run --goal "Verify harness wiring"
`loop audit` scores readiness; `loop sync` checks that your `STATE.md` and `LOOP.md` still agree. When they drift — you edit `LOOP.md` to add a loop but never wire it into `STATE.md`, or a starter update leaves one file behind — a scheduled loop can run against stale instructions. `loop doctor` runs this for you.
Copy file name to clipboardExpand all lines: docs/RELEASE.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,10 @@
1
1
# Release playbook — npm packages
2
2
3
-
This repo ships public npm packages from `tools/`. **Front door for users:**`@cobusgreyling/loop` ([cli-front-door.md](./cli-front-door.md)). Sibling packages stay published and supported.
3
+
This repo ships public npm packages from `tools/`. **Front door for users:**`@cobusgreyling/loop-cli` ([cli-front-door.md](./cli-front-door.md)). Sibling packages stay published and supported.
Copy file name to clipboardExpand all lines: docs/cli-front-door.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,20 +1,20 @@
1
-
# CLI front door — `@cobusgreyling/loop`
1
+
# CLI front door — `@cobusgreyling/loop-cli`
2
2
3
3
> **Additive.** Old packages stay fully supported. This is the recommended entry for new users, forks, and agents.
4
4
5
5
## Why
6
6
7
7
Loop Engineering ships several focused CLIs (`loop-init`, `loop-audit`, `loop-cost`, …). That is great for maintainers; it is hard for first-time adopters to remember.
8
8
9
-
`@cobusgreyling/loop` is a **thin umbrella**:
9
+
`@cobusgreyling/loop-cli` is a **thin umbrella**:
10
10
11
11
1. One binary people can remember
12
12
2.**Pass-through** to existing tools (same flags)
13
13
3.**doctor** / **status** for activation and day-2 habit
0 commit comments