gstack-upgrade

Upgrade gstack installations to the latest version across git and vendored install types.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/dhnpmp-tech/project-agent --skill gstack-upgrade-dhnpmp-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gstack-upgrade
Source: https://github.com/dhnpmp-tech/project-agent/tree/main/.claude/skills/gstack/gstack-upgrade
Command: npx skills add https://github.com/dhnpmp-tech/project-agent --skill gstack-upgrade-dhnpmp-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping gstack up to date is tedious when installs vary between global git clones, local git checkouts, and vendored copies, and manual upgrades risk losing local changes or leaving stale vendored copies behind. ## Core Features & Use Cases - Install Type Detection: Automatically detects whether gstack is installed as a global git repo, local git repo, or vendored copy, and applies the correct upgrade path. - Safe Upgrade with Rollback: Stashes local changes, backs up vendored installs, and restores from backup if the setup step fails. - Vendored Copy Sync: Detects and updates a secondary local vendored copy so global and project-level installs stay in sync. - Update Preferences: Supports auto-upgrade mode, snoozing reminders with escalating backoff, and disabling update checks entirely. - Use Case: A developer sees an UPGRADE_AVAILABLE notice while running another gstack skill; this skill asks for confirmation, upgrades the install, syncs the vendored copy, and summarizes what changed in the new version. ## 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 appropriate upgrade. Git installs are updated via git fetch and reset to origin/main, while vendored installs are replaced with a fresh clone.

How does gstack-upgrade handle different install types?

It detects four install types: global-git, local-git, vendored, and vendored-global, by checking for .git directories in known locations. Git installs use git fetch and reset, while vendored installs are swapped with a fresh shallow clone and re-set up.

What happens if the gstack upgrade fails during setup?

If the ./setup step fails, the skill restores the previous version from the .bak backup directory and warns you to retry manually. Auto-upgrade failures also trigger an automatic restore so you are never left with a broken install.

Can I enable automatic upgrades for gstack?

Yes, set auto_upgrade to true using the gstack-config binary or the GSTACK_AUTO_UPGRADE environment variable. When enabled, the skill skips the confirmation prompt and upgrades directly, restoring from backup if anything fails.

How do I snooze or disable gstack update notifications?

Choosing "Not now" writes a snooze state with escalating backoff of 24 hours, then 48 hours, then one week. Choosing "Never ask again" sets update_check to false via gstack-config, which you can re-enable at any time.

Does gstack-upgrade update vendored copies inside my project?

Yes, after upgrading the primary install it checks for a local vendored copy under .claude/skills/gstack in the current git repository. If versions differ, it syncs the vendored copy from the freshly upgraded primary install and reminds you to commit it.