gstack-upgrade

Detect gstack install type and upgrade global and vendored deployments.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/lachieh/babytalk --skill gstack-upgrade-lachieh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gstack-upgrade
Source: https://github.com/lachieh/babytalk/tree/main/.claude/skills/gstack/gstack-upgrade
Command: npx skills add https://github.com/lachieh/babytalk --skill gstack-upgrade-lachieh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Upgrade gstack to the latest version across global and vendored installs by detecting install type, performing upgrade, and reporting changes to the user.

Core Features & Use Cases

  • Detects install type (global/local, git/vendored) and upgrades accordingly.
  • Shows what's new after upgrade and gracefully handles auto-upgrade or manual prompts.
  • Syncs local vendored copies when present to keep consistency across deployments.

Quick Start

Run /gstack-upgrade to start the upgrade and view what's new.

Frequently Asked Questions about gstack-upgrade

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

FAQPage Schema
How do I upgrade gstack to the latest version?

The gstack upgrade command detects your installation type, updates global and vendored deployments, and reports changes. It supports auto-upgrade or manual prompts to keep your CLI tool current.

How does gstack handle versioning for both git-based and vendored installs?

For git-based and vendored installs, the upgrade detects the installation type, uses Git operations to update git deployments, and syncs local vendored copies to ensure versioning consistency across all environments.

Do I need Git installed to upgrade a global gstack deployment?

Git is required for upgrading git-based gstack deployments. The workflow uses Git operations to update the install directory, while vendored deployments rely on reading and modifying VERSION and CHANGELOG files.

What is the best way to see what's new after updating a devops CLI tool?

Using the gstack upgrade command is the best way to see changes, as it automatically reads the CHANGELOG file and reports what is new after successfully updating both global and vendored installations.

Why does my local vendored gstack copy not match the global version after an upgrade?

Your local vendored copy may not match because the upgrade's sync process did not complete. The upgrade workflow explicitly syncs local vendored copies with the global install to ensure versioning consistency.