gstack-upgrade

Upgrades gstack to latest version and summarizes what's new from CHANGELOG.md.

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/GS-Personal/gstack --skill gstack-upgrade-gs-personal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gstack-upgrade
Source: https://github.com/GS-Personal/gstack/tree/main/gstack-upgrade
Command: npx skills add https://github.com/GS-Personal/gstack --skill gstack-upgrade-gs-personal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Upgrade gstack to the latest version in an automated, safe manner, ensuring the installed tool stays current.

Core Features & Use Cases

  • Install-type detection: supports global-git, local-git, vendored, and vendored-global installations to locate the gstack source.
  • Version handling: reads the current VERSION file, fetches updates, and runs setup to complete the upgrade.
  • Changelog & history: reads CHANGELOG.md to summarize what's new and shows a concise user-facing summary.
  • Safety & continuity: preserves local changes by stashing when needed and records upgrade history markers for traceability.

Quick Start

Ask your automation to run /gstack-upgrade to upgrade gstack to the latest version 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?

The upgrade detects your installation type, reads the current VERSION, fetches updates, and runs setup. It preserves local changes by stashing when needed.

What's the best way to automate a version upgrade and generate a change log summary?

Automating a version upgrade requires detecting the install layout, fetching updates, and parsing CHANGELOG.md to surface a concise what's new summary.

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

The upgrade process works with global-git, local-git, vendored, and vendored-global installations by detecting the install type to locate the source correctly.

How are local changes preserved when running an automated upgrade?

Local changes are preserved during an automated upgrade by stashing them when needed and enforcing guardrails to ensure modifications remain intact.

Why should I use an automated upgrade script instead of manually pulling version control updates?

Using an automated upgrade script ensures traceability by storing upgrade history markers and reading CHANGELOG.md, whereas manual pulls lack these safety guardrails.

What limitations or precautions exist when upgrading a vendored installation?

When upgrading a vendored installation, the process must accurately detect the vendored or vendored-global layout and stash local changes before fetching updates.