gstack-upgrade

Upgrades gstack installations to the latest version via git or vendored sync.

2|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/westkite1201/garden-engine --skill gstack-upgrade-westkite1201
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gstack-upgrade
Source: https://github.com/westkite1201/garden-engine/tree/main/.claude/skills/gstack/gstack-upgrade
Command: npx skills add https://github.com/westkite1201/garden-engine --skill gstack-upgrade-westkite1201

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping a gstack installation current requires manually detecting whether it is a global git clone, a local git clone, or a vendored copy, then running the correct upgrade commands for each. This Skill automates that detection and upgrade flow, including syncing stale local vendored copies and summarizing what changed. ## Core Features & Use Cases - Install Type Detection: Identifies global-git, local-git, vendored, and vendored-global installs by checking for .git directories in known locations. - Safe Upgrade with Rollback: Stashes local changes for git installs and backs up vendored directories, restoring from backup if setup fails. - Vendored Copy Sync: Detects and updates a stale local vendored copy in the project repository to match the freshly upgraded primary install. - Update Prompting and Snoozing: Supports auto-upgrade mode, escalating snooze backoff (24h, 48h, 1 week), and permanent opt-out via config. - Use Case: When a skill preamble reports UPGRADE_AVAILABLE, run this Skill to upgrade gstack from v1.0 to v1.1, sync the vendored copy in your repo, and read a summary of the changelog highlights. ## 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, and runs the upgrade. Git installs use git fetch and reset to origin/main, while vendored installs are replaced with a fresh clone and re-set up.

How does gstack detect global versus vendored installs?

It checks for .git directories in known locations such as ~/.claude/skills/gstack and .claude/skills/gstack. A directory with .git is treated as a git install, while one without is treated as vendored.

Can gstack upgrade automatically without asking?

Yes, set auto_upgrade to true via gstack-config or the GSTACK_AUTO_UPGRADE environment variable. Auto-upgrades skip the confirmation prompt and restore from backup if setup fails.

What happens if the gstack upgrade fails during setup?

For vendored installs, the previous version is restored from the .bak backup directory and a warning is shown. For git installs, stashed local changes can be recovered with git stash pop.

How do I stop gstack update reminders?

Choose "Not now" to snooze with escalating backoff of 24h, 48h, then 1 week, or choose "Never ask again" to disable update checks via gstack-config set update_check false.