@cueloop/pi 0.1.0-alpha.92 → 0.1.0-alpha.94

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cueloop/pi",
-  "version": "0.1.0-alpha.92",
+  "version": "0.1.0-alpha.94",
   "description": "cueloop Thread integration for pi",
   "keywords": [
     "pi-package"
@@ -31,7 +31,7 @@
     "prepack": "node prepare-skills.mjs"
   },
   "dependencies": {
-    "@cueloop/adapters": "0.1.0-alpha.92"
+    "@cueloop/adapters": "0.1.0-alpha.94"
   },
   "peerDependencies": {
     "@earendil-works/pi-coding-agent": "^0.86.0"

package/skills/code-review/SKILL.md

@@ -1,6 +1,11 @@
 ---
 name: cueloop-code-review
 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\"."
+metadata:
+  credits:
+    skill: code-review
+    author: Matt Pocock
+    url: "https://github.com/mattpocock/skills/tree/c55ee46073ed923f86ce59a5eb3b6d895095d1b7/skills/engineering/code-review"
 ---
 
 Two-axis review of the diff between `HEAD` and a fixed point the user supplies:

package/skills/review/SKILL.md

@@ -13,7 +13,7 @@ Use this workflow for `/cueloop:review <pull-request>`.
    - `worktree`: create or reuse `~/.cueloop/worktrees/<owner>-<repo>/pr-<number>-<short-sha>`, fetch the head, and add it as a detached git worktree.
    - `current`: compare `git rev-parse HEAD` with `headRefOid`. Stop if they differ.
 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`.
-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. The built-in skill is vendored verbatim from [mattpocock/skills](https://github.com/mattpocock/skills/tree/c55ee46073ed923f86ce59a5eb3b6d895095d1b7/skills/engineering/code-review).
+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).
 6. Create the Thread from that workspace:
    `cueloop review <pull-request> --head-sha <headRefOid> --no-tui --brief-file <brief-file>`
 7. Record each actionable finding with `cueloop review-comment <thread-id>`. Give it:

package/skills/code-review/LICENSE

@@ -1,21 +0,0 @@
-MIT License
-
-Copyright (c) 2026 Matt Pocock
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.

package/skills/code-review/UPSTREAM.md

@@ -1,7 +0,0 @@
-Vendored verbatim from `mattpocock/skills`:
-
-- Source: https://github.com/mattpocock/skills/tree/c55ee46073ed923f86ce59a5eb3b6d895095d1b7/skills/engineering/code-review
-- Commit: `c55ee46073ed923f86ce59a5eb3b6d895095d1b7`
-- Imported: 2026-09-24
-
-The skill is distributed under the adjacent MIT license.