update-pi-extensions

스타13

포크0

업데이트2026년 6월 29일 09:25

Check the latest version of every npm package pinned in the PLUGINS list of pixi-recipes/pi-extensions/recipe.yaml and update the file in-place with any versions that are out of date. Use when asked to "update pi-extensions", "bump pi plugin versions", or "refresh pi-extensions versions".

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

출처

crusaderky

crusaderky/pixi-llm-recipes

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Steps

1. Extract pinned packages from recipe.yaml

Read pixi-recipes/pi-extensions/recipe.yaml. The plugin pins live in the build.script.env.PLUGINS value: a space/newline-separated list of <package>@<version> entries.

Also note: the recipe package version is fixed (1) and separate from the plugin versions.

For each entry, parse:

package name — the part before the last @ (e.g. pi-autoresearch, @juicesharp/rpiv-advisor)
current version — the part after the last @ (e.g. 1.5.0)

Store them as a list of (package, current_version) tuples in the order they appear.

Note: Scoped packages like @juicesharp/rpiv-advisor have the scope as part of the package name. The version is the last @<version> segment.

2. Fetch latest versions from npm registry

For each package, query the npm registry:

GET https://registry.npmjs.org/<package>/latest

Extract .version from the JSON response. If the request fails (404 or other error), skip that package and print a warning — do not modify its entry in recipe.yaml.

3. Compare and identify updates needed

For each package:

If latest_version == current_version: no change needed.
If latest_version != current_version: mark this package as needs update.

Print a summary table:

Package                          Current    Latest   Update?
──────────────────────────────── ───────── ──────── ───────
pi-autoresearch                  1.5.0     1.6.0    YES
@juicesharp/rpiv-advisor         1.18.2    1.18.2   NO

If no packages need updating, print "All packages are already at their latest version. Nothing to do." and stop.

4. Update recipe.yaml

For every package marked YES, perform an in-place edit on pixi-recipes/pi-extensions/recipe.yaml:

Replace the version in the matching <package>@<old_version> entry of the PLUGINS list with the new version.

Example edit (old text → new text):

# Old:
        pi-autoresearch@1.5.0

# New:
        pi-autoresearch@1.6.0

Preserve all comments, blank lines, indentation, and ordering exactly as they were. Only change the version number portion.

5. Report the result

Print a final summary:

Updated pi-extensions recipe.yaml:
  pi-autoresearch:      1.5.0 → 1.6.0
  pi-token-speed:       0.3.1 → 0.4.0

Skipped (no update):
  @juicesharp/rpiv-advisor:       1.18.2 (up to date)
  @juicesharp/rpiv-ask-user-question: 1.18.2 (up to date)

Skipped (fetch failed):
  <some-package>: fetch failed — check network or package name

이 저장소의 다른 Skills

같은 저장소

update-llama-cpp

crusaderky/pixi-llm-recipes

Update both llama-cpp conda recipes (source + binary) to the latest upstream release. Updates BOTH the active fork pin (beellama) and the commented-out mainline variant pin in each recipe.yaml. Use when the user wants to bump llama-cpp to a newer version.

2026-07-3013

update-herdr

crusaderky/pixi-llm-recipes

Update the herdr conda recipe to the latest stable (Linux) and preview (Windows) releases. Use when asked to "update herdr", "bump herdr", or "update the herdr recipe".

2026-07-3013

update-all

crusaderky/pixi-llm-recipes

Update everything — llama.cpp (source + binary recipes), pi-extensions npm packages, Claude Code conda recipe, herdr (stable+preview) recipe, and run `pixi update` to refresh the lockfile. Triggered by "update yourself", "update everything", or "do a full update".

2026-07-2113

llama-cpp-changelog

crusaderky/pixi-llm-recipes

Summarize changes between two versions of llama.cpp (any fork). Repo defaults to the active fork pinned in pixi-recipes/llama-cpp-source/recipe.yaml (override with `--repo owner/name`); initial version defaults to that fork's pinned version; final version defaults to the fork's latest stable release. Refs can be overridden with arbitrary git refs. Handles both upstream `bNNNN` and beellama `vX.Y.Z` tags.

2026-07-2113

update-herdr-file-viewer

crusaderky/pixi-llm-recipes

Update the herdr-file-viewer conda recipe to the latest GitHub release — bump the pinned version and refresh the SHA-256 digests for the Linux (x86_64) and Windows (x86_64) prebuilt binaries. Use when asked to "update herdr-file-viewer", "bump herdr-file-viewer", or "update the herdr-file-viewer recipe".

2026-07-1413

use-gh-cli

crusaderky/pixi-llm-recipes

Use `gh` CLI for GitHub operations (CI logs, PRs, issues, releases) instead of HTTP web fetch. GitHub API requires authentication; `web_fetch` returns limited/empty data. The `gh` CLI is pre-authenticated and available in the sandbox.

2026-06-2913

name	update-pi-extensions
description	Check the latest version of every npm package pinned in the PLUGINS list of pixi-recipes/pi-extensions/recipe.yaml and update the file in-place with any versions that are out of date. Use when asked to "update pi-extensions", "bump pi plugin versions", or "refresh pi-extensions versions".
compatibility	Requires network access to registry.npmjs.org. Designed for the pixi-llm-recipes project.
allowed-tools	WebFetch Read Edit

Steps

1. Extract pinned packages from recipe.yaml

Read pixi-recipes/pi-extensions/recipe.yaml. The plugin pins live in the build.script.env.PLUGINS value: a space/newline-separated list of <package>@<version> entries.

Also note: the recipe package version is fixed (1) and separate from the plugin versions.

For each entry, parse:

package name — the part before the last @ (e.g. pi-autoresearch, @juicesharp/rpiv-advisor)
current version — the part after the last @ (e.g. 1.5.0)

Store them as a list of (package, current_version) tuples in the order they appear.

Note: Scoped packages like @juicesharp/rpiv-advisor have the scope as part of the package name. The version is the last @<version> segment.

2. Fetch latest versions from npm registry

For each package, query the npm registry:

GET https://registry.npmjs.org/<package>/latest

Extract .version from the JSON response. If the request fails (404 or other error), skip that package and print a warning — do not modify its entry in recipe.yaml.

3. Compare and identify updates needed

For each package:

If latest_version == current_version: no change needed.
If latest_version != current_version: mark this package as needs update.

Print a summary table:

Package                          Current    Latest   Update?
──────────────────────────────── ───────── ──────── ───────
pi-autoresearch                  1.5.0     1.6.0    YES
@juicesharp/rpiv-advisor         1.18.2    1.18.2   NO

If no packages need updating, print "All packages are already at their latest version. Nothing to do." and stop.

4. Update recipe.yaml

For every package marked YES, perform an in-place edit on pixi-recipes/pi-extensions/recipe.yaml:

Replace the version in the matching <package>@<old_version> entry of the PLUGINS list with the new version.

Example edit (old text → new text):

# Old:
        pi-autoresearch@1.5.0

# New:
        pi-autoresearch@1.6.0

Preserve all comments, blank lines, indentation, and ordering exactly as they were. Only change the version number portion.

5. Report the result

Print a final summary:

Updated pi-extensions recipe.yaml:
  pi-autoresearch:      1.5.0 → 1.6.0
  pi-token-speed:       0.3.1 → 0.4.0

Skipped (no update):
  @juicesharp/rpiv-advisor:       1.18.2 (up to date)
  @juicesharp/rpiv-ask-user-question: 1.18.2 (up to date)

Skipped (fetch failed):
  <some-package>: fetch failed — check network or package name