update-pi_skill

Overview

This skill updates Pi to the latest release and only applies changes when versions have drifted. It updates the global CLI and synchronizes the Pi-related dependencies in your dotfiles, running installs only when necessary and then reporting a concise verification summary.

How this skill works

The skill resolves the latest published Pi version from npm and compares it to the globally installed CLI. If the global CLI differs, it installs the latest version. It then opens ~/.dotfiles/home/.pi/agent/package.json and ensures the three @mariozechner/pi-* dependencies share a caret range for the latest version, writing package.json only when a change is needed. bun install is executed only when package.json was modified, and a final verification prints installed versions and a short summary of actions taken.

When to use it

• You want to upgrade Pi globally and in your dotfiles to the newest release.
• You need to ensure all @mariozechner/pi-* deps in dotfiles stay aligned.
• You prefer idempotent upgrades that avoid unnecessary installs.
• You manage Pi via a dotfiles repo and treat ~/.dotfiles/home/.pi/agent as the source of truth.

Best practices

• Keep ~/.dotfiles/home/.pi/agent under version control so package.json changes are tracked.
• Run this skill from a user shell with permissions to install global npm packages.
• Check the verification summary after run to confirm global and dotfiles versions.
• Avoid manual edits to ~/.pi; always update via the dotfiles package.json to stay consistent.

Example use cases

• Automated CI step to ensure developer machines run the same Pi CLI and agent deps.
• Developer runs the skill after hearing a new Pi release to perform a safe, minimal upgrade.
• Periodic maintenance script that keeps dotfiles-aligned Pi packages up to date without extra installs.
• Onboarding script for a new machine that ensures global CLI and dotfiles deps match the latest release.