gstack-upgrade

Upgrade gstack installations across global git, local git, and vendored modes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Up-to-date gstack is critical for stability and access to the latest features and fixes. This Skill automates detecting your install type, performing a safe upgrade, and surfacing what's new across different deployment modes.

Core Features & Use Cases

  • Detects install type (global git, local git, vendored) and chooses the appropriate upgrade path.
  • Performs upgrade steps (stash, fetch, reset, run setup) or vendored replacement with migrations.
  • Runs post-upgrade migrations and shows a changelog summary for the new version.
  • Use Case: When your team relies on gstack across multiple machines and install modes, this Skill streamlines version management and ensures consistency.

Quick Start

Run /gstack-upgrade to check for upgrades and apply them automatically.

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 different install types?

To upgrade gstack to the latest version, this skill detects your installation type—global git, local git, or vendored—and coordinates the upgrade by fetching, resetting, and running setup scripts. It handles migrations automatically for a safe version transition.

What is the best way to automate gstack migration and version management on multiple machines?

Automating gstack migration and version management involves detecting the install type and running post-upgrade migrations automatically. This skill coordinates these upgrade steps across multiple machines and deployment modes, ensuring version consistency and surfacing changelog summaries.

Do I need shell access and Git to run a safe gstack upgrade?

Yes, you need shell access and Git to run a safe gstack upgrade. The upgrade process requires shell access to execute installation scripts, Git to perform fetch and reset operations for git-based installs, and migration tooling for auditable updates.

How does the upgrade process handle vendored installations differently from git installations?

For vendored installations, the upgrade process performs a complete vendored replacement with migrations rather than using git stash, fetch, and reset commands. It detects the install type and chooses the appropriate upgrade path to ensure a safe version transition.

Why does my gstack upgrade require running post-upgrade migrations and how are they applied?

Post-upgrade migrations are required during a gstack upgrade to ensure stability and access to new features. The skill runs these migrations automatically after performing the version upgrade, subsequently displaying a changelog summary for the new version.