Menu
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.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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.
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".
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".
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.
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".
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".
| name | use-gh-cli |
| description | 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. |
web_fetch / HTTP GET to github.com or api.github.com returns empty or limited data — GitHub requires authentication for most API endpoints and even web pages. This means CI logs, PR diffs, issue details, and release assets all fail via plain web fetch.
The gh CLI is on PATH inside the sandbox, but only pixi run pi -- --with-git (note the --) binds auth credentials. Unsandboxed (pi-unsafe) works too.
Before any gh command, run gh auth status. If it fails, stop immediately — no workarounds. Tell user:
ghCLI is not authenticated. Restart pi withpixi run pi <path-to-workspace> -- --with-gitto bind GitHub auth credentials. Re-run with--with-gitand try again.
Do not fall back to web_fetch or other methods.
gh InsteadWhen user pastes a CI log URL — do NOT use web_fetch. Extract owner/repo, run ID, and optional job ID from the URL, then use gh:
| URL | Pattern | gh command |
|---|---|---|
https://github.com/owner/repo/actions/runs/12345 | run ID = 12345 | gh run view 12345 --log |
https://github.com/owner/repo/actions/runs/12345/job/67890 | run ID = 12345, job ID = 67890 | gh run view 12345 --log --job 67890 |
Example: user pastes https://github.com/dask/dask/actions/runs/27794025788/job/82249639708
→ gh run view 27794025788 --log --job 82249639708
For a run-only URL: https://github.com/dask/dask/actions/runs/27794025788
→ gh run view 27794025788 --log
# List recent workflow runs for the current repo
gh run list --limit 10
# View failed runs
gh run list --limit 5 --status failure
# View logs for a specific run (interactive viewer)
gh run view <run-id> --log
# Get full log for a specific job
gh run view <run-id> --log --job <job-id>
# Get log as text (pipe to file or grep)
gh run view <run-id> --log > ci.log
gh pr view <number> # PR details + diff
gh pr view <number> --json # Full JSON for scripting
gh issue view <number> # Issue details
gh pr list --state open # Open PRs
gh release view <tag> # Release details + assets
gh release list --limit 5 # Recent releases
gh repo view # Repo details
gh repo view --json defaultBranch,description,homepageUrl
gh works in the current directory's repo context. Outside a repo, use gh <command> --repo <owner>/<repo>.gh run list --json databaseId --jq '.[0].databaseId' to extract IDs for scripting.read tool.