gstack-upgrade

Upgrade GStack installations across global git, local git, and vendored types.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/Jesse-L-M/scz-target-engine --skill gstack-upgrade-jesse-l-m
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gstack-upgrade
Source: https://github.com/Jesse-L-M/scz-target-engine/tree/main/.claude/skills/gstack/gstack-upgrade
Command: npx skills add https://github.com/Jesse-L-M/scz-target-engine --skill gstack-upgrade-jesse-l-m

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Upgrading GStack in mixed environments (global git, local git, vendored) is fragile and error-prone due to divergent install layouts, missing changelogs, and manual steps. This Skill unifies detection, backup, upgrade, and changelog presentation so upgrades are repeatable and safe.

Core Features & Use Cases

  • Detects your GStack install type (global git, local git, or vendored) and locates the correct installation directory.
  • Performs a safe upgrade workflow with stash handling, backups, and post-setup steps to ensure a clean upgrade.
  • Reads VERSION and CHANGELOG.md to summarize what's new and to surface changes for user verification before use.

Quick Start

Run /gstack-upgrade to upgrade your gstack installation 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 safely?

To upgrade gstack safely, the tool detects your specific installation type, creates backups, runs a stash-handling workflow, and re-runs setup steps to ensure a clean update across global git, local git, or vendored environments.

What is the best way to manage gstack version updates across mixed environments?

Managing gstack version updates across mixed environments is unified by detecting divergent install layouts automatically, handling stash and backups, and validating changes via changelog to ensure repeatable and safe upgrades.

Does the gstack upgrade process work with vendored and local git installations?

Yes, the gstack upgrade process works with vendored and local git installations by detecting the correct installation directory and applying a deterministic upgrade workflow tailored to each specific install type.

Why does upgrading gstack manually often fail in mixed environments?

Upgrading gstack manually fails in mixed environments due to divergent install layouts, missing changelogs, and manual steps that cause errors, which this automated workflow resolves through detection and backups.

How can I see what changes are new after a gstack version upgrade?

To see what changes are new after a gstack version upgrade, the tool reads the VERSION and CHANGELOG.md files to summarize updates and surface changes for user verification before use.

Can I run post-setup steps automatically when upgrading gstack?

Yes, you can run post-setup steps automatically when upgrading gstack, as the safe upgrade workflow includes stash handling, backups, and setup re-runs to guarantee a clean and validated installation state.