gsd-update

Detect installed GSD versions, compare with npm latest, and update after confirmation.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/hadpadrahul/school-erp --skill gsd-update-hadpadrahul
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-update
Source: https://github.com/hadpadrahul/school-erp/tree/main/.codex/skills/gsd-update
Command: npx skills add https://github.com/hadpadrahul/school-erp --skill gsd-update-hadpadrahul

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Update GSD to the latest version by detecting installed versions, comparing with npm, and surfacing changelog details to help decide whether to upgrade.

Core Features & Use Cases

  • Version detection (local/global)
  • Fetch latest version via npm
  • Compare versions
  • Fetch and display changelog
  • Warn about clean install
  • Prompt for confirmation
  • Perform update
  • Clear cache
  • Restart reminder

Quick Start

Invoke the gsd-update command to check for updates and apply the upgrade when you are ready.

Frequently Asked Questions about gsd-update

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

FAQPage Schema
How do I update my npm package to the latest version and check the changelog first?

Updating npm packages safely requires detecting the installed version, comparing it against the latest release, and displaying the changelog to review changes before confirming the update execution and clearing the cache.

What is the safest way to apply version updates for development environments?

Safe version updates for development environments involve fetching the latest release details, surfacing changelog information to help decide whether to upgrade, and prompting for explicit user confirmation before applying any changes.

How do I check the installed version of an npm package locally and globally before upgrading?

Checking installed npm package versions involves local and global version detection, comparing those versions against the npm latest release, and warning about clean install requirements before proceeding.

Does this update workflow prompt for confirmation before applying changes?

Yes, this update workflow prompts for explicit user confirmation after displaying the changelog and warning about clean installs, ensuring you decide whether to upgrade before it executes the update and clears the cache.

Why do I need to clear cache and restart after applying an npm update?

Clearing cache and restarting after an npm update ensures the environment fully recognizes the newly installed package version, preventing conflicts from previous version remnants and completing the safe upgrade workflow.