@cueloop/pi 0.1.0-alpha.91 → 0.1.0-alpha.93
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
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@cueloop/pi",
|
|
3
|
-
"version": "0.1.0-alpha.
|
|
3
|
+
"version": "0.1.0-alpha.93",
|
|
4
4
|
"description": "cueloop Thread integration for pi",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"pi-package"
|
|
@@ -31,7 +31,7 @@
|
|
|
31
31
|
"prepack": "node prepare-skills.mjs"
|
|
32
32
|
},
|
|
33
33
|
"dependencies": {
|
|
34
|
-
"@cueloop/adapters": "0.1.0-alpha.
|
|
34
|
+
"@cueloop/adapters": "0.1.0-alpha.93"
|
|
35
35
|
},
|
|
36
36
|
"peerDependencies": {
|
|
37
37
|
"@earendil-works/pi-coding-agent": "^0.86.0"
|
|
@@ -1,6 +1,11 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: cueloop-code-review
|
|
3
3
|
description: "Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to \"review since X\"."
|
|
4
|
+
metadata:
|
|
5
|
+
credits:
|
|
6
|
+
skill: code-review
|
|
7
|
+
author: Matt Pocock
|
|
8
|
+
url: "https://github.com/mattpocock/skills/tree/c55ee46073ed923f86ce59a5eb3b6d895095d1b7/skills/engineering/code-review"
|
|
4
9
|
---
|
|
5
10
|
|
|
6
11
|
Two-axis review of the diff between `HEAD` and a fixed point the user supplies:
|
package/skills/pair/SKILL.md
CHANGED
|
@@ -8,13 +8,12 @@ disable-model-invocation: true
|
|
|
8
8
|
|
|
9
9
|
Start pairing in the current repository. The user stays in control of which code changes.
|
|
10
10
|
|
|
11
|
-
1.
|
|
11
|
+
1. As your first action, run `cueloop pair --open-tab --no-tui`. Parse its JSON `threadId`, `startedAt`, and `openStatus`. This finds or creates the repo's live workbench Thread and immediately opens its pairing UI in a focused Herdr tab. Its daemon watches the checkout through the configured VCS adapter, so Git, JJ, or another configured VCS appears in the Changes editor as it changes. If `openStatus` is not `opened` or `focused`, open `cueloop pair <threadId>` with the host's terminal tab control.
|
|
12
12
|
2. Read the Thread and remember the current history entry IDs. Start `cueloop session events <threadId> --ready` as a long-running command and wait for its `events.ready` JSON line. The event stream subscribes before it reads the Thread. Read the Thread again after readiness and reconcile any entries added since the first read. This catches activity in the gap before subscription.
|
|
13
|
-
3.
|
|
14
|
-
4.
|
|
15
|
-
5.
|
|
16
|
-
6.
|
|
17
|
-
7. If `session events` exits because the daemon disconnected, restart it with `--ready`. Once ready, read the Thread and reconcile all history entries since the last read before processing more events. The command exits with an error when its connection closes, so it cannot silently leave the agent waiting.
|
|
13
|
+
3. Build a queue from human-authored annotations in history order. Track processed annotation IDs in your context. Handle one item at a time, then reconcile the Thread again before waiting for another event.
|
|
14
|
+
4. Decide whether each comment requests a code change or asks for an answer. Use your language judgment for this first version. For a code change, follow the instruction with the host's edit tools and leave the annotation open. For a question, reply in that annotation's discussion as author `agent`; keep the comment open. Do not add annotations about your own code edits.
|
|
15
|
+
5. After each event, read the Thread and reconcile history. A `message` history entry created after `startedAt` ends pairing, even when its body is empty or the Thread remains pending. Stop the event stream when this happens.
|
|
16
|
+
6. If `session events` exits because the daemon disconnected, restart it with `--ready`. Once ready, read the Thread and reconcile all history entries since the last read before processing more events. The command exits with an error when its connection closes, so it cannot silently leave the agent waiting.
|
|
18
17
|
|
|
19
18
|
If the user leaves several comments while you are editing, finish the current item and then work through the rest in history order. Every human comment is one backlog item, either an edit or a reply.
|
|
20
19
|
|
package/skills/review/SKILL.md
CHANGED
|
@@ -13,7 +13,7 @@ Use this workflow for `/cueloop:review <pull-request>`.
|
|
|
13
13
|
- `worktree`: create or reuse `~/.cueloop/worktrees/<owner>-<repo>/pr-<number>-<short-sha>`, fetch the head, and add it as a detached git worktree.
|
|
14
14
|
- `current`: compare `git rev-parse HEAD` with `headRefOid`. Stop if they differ.
|
|
15
15
|
4. Write a short review brief with the PR title, a `## TL;DR` of two to four bullets, and the original body under `## PR description`.
|
|
16
|
-
5. Run the configured review skill in that workspace. Give it the PR base SHA as its fixed point, the PR body as its spec source, and the existing review comments as deduplication context. For the built-in `code-review` skill, this context is complete: use `gh issue view` for issue references and do not require repository-specific issue-tracker setup.
|
|
16
|
+
5. Run the configured review skill in that workspace. Give it the PR base SHA as its fixed point, the PR body as its spec source, and the existing review comments as deduplication context. For the built-in `code-review` skill, this context is complete: use `gh issue view` for issue references and do not require repository-specific issue-tracker setup. Its review instructions are vendored verbatim from [mattpocock/skills](https://github.com/mattpocock/skills/tree/c55ee46073ed923f86ce59a5eb3b6d895095d1b7/skills/engineering/code-review).
|
|
17
17
|
6. Create the Thread from that workspace:
|
|
18
18
|
`cueloop review <pull-request> --head-sha <headRefOid> --no-tui --brief-file <brief-file>`
|
|
19
19
|
7. Record each actionable finding with `cueloop review-comment <thread-id>`. Give it:
|
|
@@ -1,21 +0,0 @@
|
|
|
1
|
-
MIT License
|
|
2
|
-
|
|
3
|
-
Copyright (c) 2026 Matt Pocock
|
|
4
|
-
|
|
5
|
-
Permission is hereby granted, free of charge, to any person obtaining a copy
|
|
6
|
-
of this software and associated documentation files (the "Software"), to deal
|
|
7
|
-
in the Software without restriction, including without limitation the rights
|
|
8
|
-
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
|
9
|
-
copies of the Software, and to permit persons to whom the Software is
|
|
10
|
-
furnished to do so, subject to the following conditions:
|
|
11
|
-
|
|
12
|
-
The above copyright notice and this permission notice shall be included in all
|
|
13
|
-
copies or substantial portions of the Software.
|
|
14
|
-
|
|
15
|
-
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
16
|
-
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
17
|
-
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
|
18
|
-
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
19
|
-
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
|
20
|
-
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
|
|
21
|
-
SOFTWARE.
|
|
@@ -1,7 +0,0 @@
|
|
|
1
|
-
Vendored verbatim from `mattpocock/skills`:
|
|
2
|
-
|
|
3
|
-
- Source: https://github.com/mattpocock/skills/tree/c55ee46073ed923f86ce59a5eb3b6d895095d1b7/skills/engineering/code-review
|
|
4
|
-
- Commit: `c55ee46073ed923f86ce59a5eb3b6d895095d1b7`
|
|
5
|
-
- Imported: 2026-09-24
|
|
6
|
-
|
|
7
|
-
The skill is distributed under the adjacent MIT license.
|