gpd-update

Checks for GPD updates, installs the latest release, and displays changelog notes.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/MichaelsEngineering/sentinel-multiscale-field-dynamics --skill gpd-update-michaelsengineering
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gpd-update
Source: https://github.com/MichaelsEngineering/sentinel-multiscale-field-dynamics/tree/main/.agents/skills/gpd-update
Command: npx skills add https://github.com/MichaelsEngineering/sentinel-multiscale-field-dynamics --skill gpd-update-michaelsengineering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping the Get Physics Done (GPD) runtime current requires manually checking npm for new releases, comparing versions, and reinstalling with the correct runtime and scope flags. This Skill automates that entire update workflow while showing what changed before you commit. ## Core Features & Use Cases - Version Detection and Comparison: Reads the installed version from the runtime's VERSION file and semantically compares it against the latest npm registry release. - Changelog Preview: Fetches recent GitHub release notes covering versions newer than your install so you can review changes before updating. - Safe Reinstall with Confirmation: Warns that managed GPD files will be replaced, backs up local modifications to gpd-local-patches, and asks for confirmation exactly once before running the public bootstrap command. - Use Case: You see an update indicator in your AI agent and want to upgrade GPD without losing custom patches or guessing the correct install command for your runtime and scope. ## Quick Start Ask the agent to check for GPD updates and install the latest version if one is available.

Frequently Asked Questions about gpd-update

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

FAQPage Schema
How do I update GPD to the latest version?▼

Run the gpd-update workflow, which detects your installed version, checks the npm registry for the latest get-physics-done release, shows recent release notes, and reinstalls using the public bootstrap command after your confirmation.

How does GPD update checking work with local vs global installs?▼

The workflow detects install scope from the runtime's VERSION file location and config directory. Local installs use the --local flag with a target directory, while global installs use --global, and the correct update command is constructed automatically.

Will updating GPD overwrite my custom modifications?▼

Managed GPD files are replaced during update, but direct modifications to managed files are backed up to the gpd-local-patches directory. After updating, you can reapply them with the gpd-reapply-patches command.

What happens if the GPD update check fails offline?▼

If the npm registry is unreachable, the workflow reports that it could not check for updates and displays the manual update command for your runtime and scope. It then exits without making any changes.

Why does the update indicator still show after updating GPD?▼

The workflow clears cached update-check files from the local, global, and user cache directories after a successful update. You also need to restart your AI agent so it picks up the new command files.