gstack-upgrade

Automate gstack upgrades across global, local git, and vendored installs.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/mulyoved/awesome-agent-ides --skill gstack-upgrade-mulyoved
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gstack-upgrade
Source: https://github.com/mulyoved/awesome-agent-ides/tree/main/.agents/skills/gstack/gstack-upgrade
Command: npx skills add https://github.com/mulyoved/awesome-agent-ides --skill gstack-upgrade-mulyoved

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Auto-upgrading gstack is complex due to multiple install types (global/local git and vendored) and the need to surface new features. This Skill automates that lifecycle, handling safety backups, stash/restore, and clear user messaging.

Core Features & Use Cases

  • Detects install type (global/local git or vendored) and directs the upgrade accordingly.
  • Performs upgrade steps or vendored replacement with safety backups and clear prompts.
  • Syncs local vendored copies post-upgrade and reports status to ensure consistency.
  • Writes upgrade markers and clears caches to guarantee a clean starting state.
  • Provides standalone usage to manually trigger update checks and perform upgrades.

Quick Start

Run /gstack-upgrade to upgrade gstack to the latest version and review the What's New section.

Frequently Asked Questions about gstack-upgrade

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I upgrade a git clone or vendored copy to the latest version?

To upgrade a git clone or vendored copy, run the auto-upgrade flow which detects the install type, performs safety backups, handles stash/restore, and syncs local vendored copies to the latest version automatically.

How does install type detection work for global and local git repositories?

Install type detection identifies whether the installation is a global git clone, local git clone, or vendored copy, then directs the upgrade process accordingly to ensure the correct update mechanism is applied.

Can I automate version management and auto-updates for my local git clone?

Yes, you can enable auto-updates for a local git clone. The automation flow detects the install type, manages stash handling, applies the upgrade, and clears caches to guarantee a clean starting state.

What happens to uncommitted changes when performing a version upgrade?

During a version upgrade, uncommitted changes are managed through stash handling, which safely stashes your work before the upgrade and restores it afterward to prevent data loss.

How do I see what's new after upgrading to the latest version?

After upgrading to the latest version, the tool surfaces what's new by summarizing the changelog, allowing you to review new features and changes immediately post-upgrade.

Why does my vendored copy need synchronization after an upgrade?

Vendored copies require synchronization after an upgrade to ensure local files match the updated source, preventing version drift and maintaining consistency across your project dependencies.