gstack-upgrade

Automate safe gstack upgrades across global and vendored installations.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Upgrading the gstack tool across global or vendored installations can be error-prone due to mixed environments, missing migrations, and stale vendored copies. This Skill provides a safe, repeatable workflow to detect install type, perform upgrade, apply version migrations, and keep related copies in sync.

Core Features & Use Cases

  • Install-type detection: identifies whether gstack is installed globally (git), vendored, or locally, and selects the correct upgrade path.
  • Safe upgrade workflow: handles stashing local changes, resetting to the latest main branch, running setup, and rolling back on failure if needed.
  • Version migrations: runs migration scripts to align configurations and state between old and new versions.
  • Vendored-sync (local copies): propagates upgrades to local vendored copies when team mode is off, or removes stale vendored copies when team mode is on.

Quick Start

Run the /gstack-upgrade command to check for available upgrades and follow the prompts to complete the upgrade.

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 safely when using a mix of global and vendored installations?

You can automate gstack version migrations by running migration scripts that align configurations and state between old and new versions. The upgrade workflow detects your installation type and executes the necessary migrations automatically.

What happens to stale local copies during a gstack version upgrade?

During a gstack version upgrade, stale vendored copies are either propagated with the latest changes when team mode is off, or removed entirely when team mode is on. This ensures your local copies stay in sync or are cleaned up.

Can I roll back a failed gstack upgrade if the migration breaks my configuration?

Yes, you can roll back a failed gstack upgrade because the workflow includes error rollback functionality. If the setup or migration process fails, the system reverts your installation to its previous state to prevent breaking your configuration.

How does team-mode coordination affect gstack upgrades and local vendored copies?

Team-mode coordination affects gstack upgrades by removing stale local vendored copies when team mode is enabled. When disabled, the upgrade process propagates the new version to your local vendored copies to keep them synced.

Why does my gstack upgrade fail when I have local git changes in my installation directory?

A gstack upgrade can fail with local git changes if the stashing or reset process encounters conflicts. The safe upgrade workflow attempts to stash local changes and reset to the latest main branch, rolling back automatically if these git operations fail.