@cogit/cli 0.26.0 → 0.28.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/package.json
CHANGED
package/skills/record/SKILL.md
CHANGED
|
@@ -15,7 +15,7 @@ The current record (`cogit session show`):
|
|
|
15
15
|
- `initialized: false`: reply exactly "cogit is not set up in this project yet; run
|
|
16
16
|
`npx @cogit/cli init` here first." and stop.
|
|
17
17
|
- `sessionError`: quote it and stop; never write over the record.
|
|
18
|
-
- Nothing new or changed (`newMessages` empty): reply "
|
|
18
|
+
- Nothing new or changed (`newMessages` empty): reply "cogit is up to date." and stop.
|
|
19
19
|
|
|
20
20
|
## Look something up
|
|
21
21
|
|
|
@@ -36,8 +36,11 @@ One JSON object:
|
|
|
36
36
|
|
|
37
37
|
- `sessionId`: always `"${CLAUDE_SESSION_ID}"`.
|
|
38
38
|
- `title`: a few words; on the first write or when the focus changed.
|
|
39
|
-
- `status`: replaces all four fields, so send each: `goal` (one sentence), `done
|
|
40
|
-
|
|
39
|
+
- `status`: replaces all four fields, so send each: `goal` (one sentence), `done` (what
|
|
40
|
+
finished, as outcomes), `pending` (the work still open, one item per ask in the user's
|
|
41
|
+
words — never a checklist of commands; a release and the restart it needs are one item, and
|
|
42
|
+
a step that serves nothing is dropped; `{ "text", "needsUser": true }` when it waits on the
|
|
43
|
+
user), `next` (concrete step).
|
|
41
44
|
- `nodes`: only new nodes or changed fields; the rest is kept.
|
|
42
45
|
|
|
43
46
|
## One node per user message
|
|
@@ -154,4 +157,4 @@ personal data, file contents or command output.
|
|
|
154
157
|
2. `node "${CLAUDE_PLUGIN_ROOT}/dist/cli.js" session write -C "<dir from the record>" --file "<inbox path>" --consume`
|
|
155
158
|
|
|
156
159
|
If it fails, fix the JSON according to the error and run it again. Then reply with one short
|
|
157
|
-
line, e.g. "
|
|
160
|
+
line, e.g. "cogit updated (3 nodes)"; never repeat the JSON.
|