gsd-update

Determines installed GSD version, compares with npm latest, performs validated upgrade with cache clearing and restart reminder.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/novatech2210-cmd/ImidusApp --skill gsd-update-novatech2210-cmd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-update
Source: https://github.com/novatech2210-cmd/ImidusApp/tree/main/.codex/skills/gsd-update
Command: npx skills add https://github.com/novatech2210-cmd/ImidusApp --skill gsd-update-novatech2210-cmd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Determine the installed GSD version and location to decide if an update is needed.

Core Features & Use Cases

  • Version detection (local vs global) to determine install state.
  • Latest version lookup via npm and changelog retrieval for review.
  • Safe upgrade flow with user confirmation, cache clearing, and restart reminder.

Quick Start

Run the gsd-update workflow to check for the latest version, display the changelog, and perform the update with cache clearing.

Frequently Asked Questions about gsd-update

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

FAQPage Schema
How do I check the installed npm version and see if an update is needed?

The workflow detects your installed version and location, compares it against available versions on npm, and determines whether an upgrade is required to update your package.

Can I view the changelog before installing the latest npm package update?

Yes, the workflow fetches and displays the changelog for the latest release prior to asking for your confirmation to perform the package update.

Does the update process clear the cache and remind me to restart?

The update process clears caches after validating user confirmation and performing the upgrade, and it provides a reminder about a restart if required.

What is the best way to safely upgrade a globally installed npm package?

A safe upgrade workflow evaluates the installed version, fetches the changelog, requests user confirmation, performs the upgrade, and clears the cache automatically.

Why does my npm package update require a restart after installation?

A restart is required after installation when the updated package needs to clear its cache and reload core processes to apply the newly installed version changes effectively.