taskforce-loop-engineering 0.7.0 → 0.7.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,12 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.7.1 - 2026-08-05
|
|
4
|
+
|
|
5
|
+
- Make the standalone ClawHub skill self-sufficient by documenting the official npm package, GitHub repository, Node.js requirement, license, and installation commands.
|
|
6
|
+
- Distinguish installing the skill, installing the CLI, and integrating the CLI with OpenClaw.
|
|
7
|
+
- Add plan, confirmed install, doctor, and disposable smoke commands for a verifiable OpenClaw deployment.
|
|
8
|
+
- Require checking an exact workspace source path before using the source-only CLI fallback.
|
|
9
|
+
|
|
3
10
|
## 0.7.0 - 2026-08-05
|
|
4
11
|
|
|
5
12
|
- Rename the project, npm package, GitHub repository, and bundled skill to Taskforce Loop Engineering.
|
package/package.json
CHANGED
|
@@ -9,6 +9,85 @@ Use this skill only when the user explicitly invokes Loop Engineering, says `走
|
|
|
9
9
|
|
|
10
10
|
Do not route ordinary chat, research, explanations, or simple direct tasks into a loop unless the user explicitly invokes it.
|
|
11
11
|
|
|
12
|
+
## Distribution and CLI Installation
|
|
13
|
+
|
|
14
|
+
A ClawHub installation may provide only this `SKILL.md`; it does **not** prove that the Loop Engineering CLI or OpenClaw integration is installed. Before running loop commands, check the deployment explicitly:
|
|
15
|
+
|
|
16
|
+
```bash
|
|
17
|
+
command -v loop-engineering
|
|
18
|
+
loop-engineering --help
|
|
19
|
+
```
|
|
20
|
+
|
|
21
|
+
Official distribution:
|
|
22
|
+
|
|
23
|
+
- npm package: `taskforce-loop-engineering`
|
|
24
|
+
- GitHub repository: `https://github.com/ambitioncn/taskforce-loop-engineering`
|
|
25
|
+
- ClawHub skill: `https://clawhub.ai/ambitioncn/skills/taskforce-loop-engineering`
|
|
26
|
+
- license: Apache-2.0
|
|
27
|
+
- runtime requirement: Node.js 22 or newer
|
|
28
|
+
|
|
29
|
+
Install the CLI globally from npm:
|
|
30
|
+
|
|
31
|
+
```bash
|
|
32
|
+
node --version
|
|
33
|
+
npm install -g taskforce-loop-engineering
|
|
34
|
+
loop-engineering --help
|
|
35
|
+
```
|
|
36
|
+
|
|
37
|
+
For a temporary read-only invocation without a global install:
|
|
38
|
+
|
|
39
|
+
```bash
|
|
40
|
+
npx -p taskforce-loop-engineering loop-engineering --help
|
|
41
|
+
```
|
|
42
|
+
|
|
43
|
+
For source-based development, clone the official repository and install its dependencies:
|
|
44
|
+
|
|
45
|
+
```bash
|
|
46
|
+
git clone https://github.com/ambitioncn/taskforce-loop-engineering.git
|
|
47
|
+
cd taskforce-loop-engineering
|
|
48
|
+
npm install
|
|
49
|
+
npm run check
|
|
50
|
+
node bin/loop-engineering.mjs --help
|
|
51
|
+
```
|
|
52
|
+
|
|
53
|
+
Do not guess a workspace source path. Use `node packages/loop-engineering/bin/loop-engineering.mjs ...` only after confirming that exact path exists in the current workspace.
|
|
54
|
+
|
|
55
|
+
### OpenClaw Integration
|
|
56
|
+
|
|
57
|
+
Installing the npm package exposes the CLI, but it does not automatically route conversations, select a worker agent, or create queue wrappers. First generate a read-only installation plan:
|
|
58
|
+
|
|
59
|
+
```bash
|
|
60
|
+
loop-engineering-openclaw-install \
|
|
61
|
+
--root /path/to/openclaw/workspace \
|
|
62
|
+
--queue agent-tasks
|
|
63
|
+
```
|
|
64
|
+
|
|
65
|
+
Review the detected agents and planned files. Then install with an existing worker-agent id:
|
|
66
|
+
|
|
67
|
+
```bash
|
|
68
|
+
loop-engineering-openclaw-install \
|
|
69
|
+
--root /path/to/openclaw/workspace \
|
|
70
|
+
--queue agent-tasks \
|
|
71
|
+
--worker-agent main \
|
|
72
|
+
--confirm-install
|
|
73
|
+
```
|
|
74
|
+
|
|
75
|
+
The installer never creates the worker agent. After installation, verify wiring before using a real task:
|
|
76
|
+
|
|
77
|
+
```bash
|
|
78
|
+
loop-engineering-openclaw-doctor \
|
|
79
|
+
--root /path/to/openclaw/workspace \
|
|
80
|
+
--queue agent-tasks \
|
|
81
|
+
--worker-agent main
|
|
82
|
+
|
|
83
|
+
loop-engineering-openclaw-smoke \
|
|
84
|
+
--root /path/to/openclaw/workspace \
|
|
85
|
+
--queue agent-tasks \
|
|
86
|
+
--worker-agent main
|
|
87
|
+
```
|
|
88
|
+
|
|
89
|
+
If the CLI or integration is missing and the user requested installation or repair, install it within the authorized host/workspace scope, then run doctor and the disposable smoke. If the user only asked what is missing, report the exact package, repository, commands, and current deployment state without mutating the system.
|
|
90
|
+
|
|
12
91
|
## Conversation Contract
|
|
13
92
|
|
|
14
93
|
Interpret explicit loop language as follows:
|