gstack-upgrade

Upgrade gstack installations across global, local, or vendored copies.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Upgrades gstack to the latest version across global, local, and vendored installations, preserving user changes and minimizing downtime.

Core Features & Use Cases

  • Detects install type (global vs vendored, Git-based vs local).
  • Upgrades the appropriate copy, runs post-upgrade migrations, and syncs local vendored copies.
  • Surface what's new after the upgrade and provide a safe rollback path if issues arise.

Quick Start

Run the upgrade command to apply the latest gstack 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 across different install types without losing my changes?

To upgrade gstack safely, the process detects your install type—global, local, or vendored—and applies Git-based upgrades or vendored synchronization while preserving your local changes.

What happens to my vendored gstack copy when I upgrade to a new version?

Upgrading a vendored gstack copy synchronizes your local files with the latest version, ensuring your custom modifications are preserved during the version migration process.

Does gstack upgrade support post-upgrade migrations and rollback?

Yes, the gstack upgrade runs necessary post-upgrade migrations automatically and provides a safe rollback path, surfacing what's new after the upgrade to keep you informed.

What's the best way to manage Git-based gstack installations during an upgrade?

For Git-based installations, the upgrade automates pulling the latest version and running migrations, enforcing a change-safe workflow that detects the install type before performing the Git upgrade.

Why does my gstack upgrade need to detect the install type first?

Detecting the install type first ensures the upgrade targets the correct copy—whether global, local, or vendored—preventing data loss and ensuring the right migration steps are applied.