update-pi

Update the global Pi CLI and dotfiles dependencies when drift is detected.

Updated Jun 22, 2024
One-click install
npx skills add https://github.com/Dyrean/dotfiles --skill update-pi-dyrean
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-pi
Source: https://github.com/Dyrean/dotfiles/tree/main/pi/.pi/agent/skills/update-pi
Command: npx skills add https://github.com/Dyrean/dotfiles --skill update-pi-dyrean

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates keeping Pi up to date by updating the global CLI and dotfiles agent dependencies only when versions drift, minimizing unnecessary changes.

Core Features & Use Cases

  • Automated drift detection: Checks the latest Pi release and compares it to the current global CLI version, updating only if needed.
  • Dependency synchronization: Aligns @mariozechner/pi-* dependencies in ~/.dotfiles/home/.pi/agent/package.json as drift is detected.
  • Idempotent execution: Runs install steps (bun install) only when changes occur, preserving stability.

Quick Start

Use this skill to ensure your Pi environment stays in sync with the latest release.

Frequently Asked Questions about update-pi

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically update Pi CLI dependencies when versions drift?

Version drift detection compares the latest Pi release to your global CLI, updating @mariozechner/pi-* dependencies in ~/.dotfiles/home/.pi/agent/package.json and running bun install only when package.json changes.

What is version drift detection for npm package.json dependencies?

Version drift detection checks the latest Pi release against the current global CLI version, ensuring dependencies are synchronized only when an actual mismatch is identified to minimize unnecessary changes.

Do I need bun and node installed to update my Pi environment?

Yes, you need npm, bun, and node tooling available on your system to determine versions, apply updates to package.json, and verify the final state of the Pi environment.

What's the best way to keep dotfiles agent dependencies in sync?

Idempotent execution aligns @mariozechner/pi-* dependencies in ~/.dotfiles/home/.pi/agent/package.json and re-runs bun install only when drift is detected, preserving stability without unnecessary changes.

Why does my Pi update process run install steps even when nothing changes?

This issue occurs without idempotent checks; this skill runs bun install only when package.json actually changes due to drift, preventing unnecessary install steps and preserving environment stability.

Can I use this to update Pi globally without modifying unrelated dotfiles?

Yes, it applies updates specifically to the global Pi CLI and syncs dotfiles agent dependencies in ~/.dotfiles/home/.pi/agent/package.json, leaving unrelated dotfiles untouched.