gstack-upgrade

Detect gstack install type and apply the appropriate upgrade flow.

2|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/nicholaslocascio/x-claw-studio --skill gstack-upgrade-nicholaslocascio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gstack-upgrade
Source: https://github.com/nicholaslocascio/x-claw-studio/tree/main/skills/gstack/gstack-upgrade
Command: npx skills add https://github.com/nicholaslocascio/x-claw-studio --skill gstack-upgrade-nicholaslocascio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Upgrade gstack across diverse deployment modes is error-prone and risky without guidance; this Skill automates the upgrade flow to ensure a safe, repeatable update.

Core Features & Use Cases

  • Detects install type (global-git, local-git, vendored, or vendored-global) and runs the appropriate upgrade path.
  • Upgrades to the latest release, shows what’s new, and synchronizes any local vendored copies.
  • Handles edge cases like local changes and auto-upgrade preferences, with clear user prompts and fallbacks.

Quick Start

Run /gstack-upgrade to trigger the upgrade flow and verify the new 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 safely?

The gstack upgrade process detects whether your install is global-git, local-git, or vendored. It then applies the appropriate CLI-based update flow, syncs local vendored copies, updates caches, and displays a summarized changelog of what's new in the release.

Does the gstack upgrade flow work for vendored and global deployments?

Yes, the upgrade flow supports global-git, local-git, vendored, and vendored-global deployments. It detects your installation type and runs the matching CLI-based update path, including syncing local vendored copies to ensure consistency across diverse deployment modes.

What is the best way to handle local changes before updating gstack?

The automated upgrade flow handles edge cases like local changes by providing clear user prompts and fallbacks. This ensures the gstack update does not overwrite unsaved work without confirmation, maintaining a safe and repeatable upgrade process.

Why does upgrading gstack require an install type detection step?

Install type detection is required because diverse deployment modes need different update paths. Identifying whether the gstack install is global-git, local-git, or vendored ensures the upgrade flow applies the correct CLI commands and safely syncs the appropriate caches.

What are the limitations of automating CLI upgrades for gstack?

A key limitation of automating CLI upgrades is resolving local changes in git-based or vendored deployments. The automated gstack flow mitigates this by using clear user prompts and fallbacks, but manual intervention may still be needed to resolve complex conflicts.