gstack-upgrade

Automate gstack upgrades by detecting global, local, or vendored install locations.

8|2|Updated Mar 24, 2026

Search Tags:#agent workflow #maintenance #upgrade #automation tooling #gstack #changelog summary #install detection

Ready to run

npx skills add https://github.com/MFS-code/gstack --skill gstack-upgrade-mfs-code

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gstack-upgrade
Source: https://github.com/MFS-code/gstack/tree/main/gstack-upgrade
Command: npx skills add https://github.com/MFS-code/gstack --skill gstack-upgrade-mfs-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of keeping gstack up to date safely and manually, without having to figure out which install location you’re using or what changed between versions.

Core Features & Use Cases

Manual, user-controlled upgrade: Runs only when the user invokes /gstack-upgrade, with an option to enable future auto-upgrades.
Accurate install detection: Detects global vs local vs vendored installations and upgrades the correct directory.
Change summary for confidence: Reads CHANGELOG.md and summarizes user-facing updates in clear grouped bullets.
Recovery when things go wrong: Uses backups for vendored installs and can restore previous versions if setup fails.

Quick Start

Ask your agent to run the manual upgrade by typing: /gstack-upgrade.

Frequently Asked Questions about gstack-upgrade

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

FAQPage Schema

How do I manually upgrade my CLI tool installation to the latest version?▼

To manually upgrade your installation, invoke the command to trigger a user-controlled flow that detects your specific install location and updates it to the latest version. This ensures your tool stays current without guessing directories.

How does install detection work for upgrading global, local, or vendored directories?▼

Install detection works by automatically scanning your environment to identify whether the installation is global, local, or vendored, then targeting the correct directory for the upgrade. This prevents applying updates to the wrong location.

Can I see a changelog summary of what changed after an upgrade?▼

Yes, after completing the upgrade, the tool reads the CHANGELOG file and summarizes user-facing updates in clear grouped bullets. This changelog summary provides confidence by highlighting what changed between versions.

What happens if a vendored setup upgrade fails?▼

If a vendored setup upgrade fails, the tool uses backups to restore the previous version. This recovery mechanism ensures your environment reverts safely when things go wrong during the update process.

Can I enable automatic upgrades after running a manual update?▼

You can enable optional auto-upgrade behavior with user confirmation during a manual update. This allows future updates to run automatically while providing snooze and backoff options to control frequency.

Do I need to stash or reset changes before upgrading a local installation?▼

Yes, upgrading a local installation requires stashing or resetting changes to manage version-marker writing and replace logic. This ensures the upgrade process applies cleanly without conflicting with local modifications.