gstack-upgrade

Detect gstack install type and upgrade global, local, and vendored copies.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Upgrade management for gstack across global vs vendored and local installs, simplifying the process of staying on the latest release.

Core Features & Use Cases

  • Detect install type (global git, local git, vendored) and determine upgrade path.
  • Upgrade installed gstack automatically or manually, with safeguards and rollback prompts.
  • Sync local vendored copies after upgrade and present a changelog summary.

Quick Start

Run /gstack-upgrade to check for updates and install the latest version.

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 across multiple installation types?

To upgrade gstack, use automation to detect your install type—global git, local git, or vendored—and apply the correct upgrade path. This process identifies old versus new versions and reports the changelog summary automatically.

What is the best way to sync local vendored copies after a gstack version upgrade?

Syncing local vendored copies after a gstack version upgrade is handled automatically by the upgrade workflow. It applies the upgrade path and optionally synchronizes your local files to match the latest release.

Does the gstack upgrade process include rollback safeguards if the new version breaks my devops automation?

Yes, the gstack upgrade process includes safeguards and rollback prompts. If the new version introduces breaking changes to your devops automation, you are prompted to revert before finalizing the upgrade.

How do I check what's new in gstack before applying an automated upgrade?

Checking what's new in gstack before upgrading involves running the upgrade command, which compares old versus new versions and presents a changelog summary detailing the updates before applying the final upgrade path.

When should I manually upgrade gstack instead of using automated bash automation?

You should manually upgrade gstack instead of using bash automation when you need strict control over the deployment pipeline. The automated workflow supports manual intervention with safeguards and rollback prompts for complex environments.