gstack-upgrade

Upgrades gstack installations to the latest version and summarizes changelog entries.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping a gstack installation current requires manually detecting the install type, pulling updates, running setup, and reconciling vendored copies. This Skill automates that entire upgrade workflow and reports what changed. ## Core Features & Use Cases - Install Detection: Identifies global-git, local-git, vendored, and vendored-global install layouts before upgrading. - Safe Upgrade Flow: Stashes local changes, backs up vendored copies, runs setup, and restores from backup on failure. - Version Migrations & Changelog: Runs versioned migration scripts and summarizes user-facing changes between old and new versions. - Use Case: When a skill preamble reports UPGRADE_AVAILABLE, invoke this Skill to confirm with the user, upgrade the install, sync any local vendored copy, and display a What's New summary. ## Quick Start Ask the assistant to upgrade gstack to the latest version and show what is 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?

Invoke the /gstack-upgrade skill, which forces a fresh update check, detects your install type, pulls or re-clones the latest code, runs setup, and shows a What's New summary of changes between versions.

How does gstack detect global versus vendored installs?

The upgrade flow checks for .git directories under ~/.claude/skills/gstack, ~/.gstack/repos/gstack, and project-level .claude or .agents skill folders. Git-based installs use git fetch and reset, while vendored installs are replaced with a fresh clone.

Can gstack upgrade automatically without asking?

Yes. Setting auto_upgrade to true via gstack-config or the GSTACK_AUTO_UPGRADE environment variable skips the confirmation prompt. If the automatic upgrade fails, the previous version is restored from backup.

What happens if the gstack upgrade fails?

For vendored installs, the previous directory is preserved as a .bak backup and restored if setup fails. For git installs, local changes are stashed before the reset and can be recovered with git stash pop.

How do I stop gstack update notifications?

Choose Not now to snooze reminders with escalating backoff of 24 hours, 48 hours, then one week. Choose Never ask again to set update_check to false via gstack-config, which disables update checks entirely.