gstack-upgrade

Automate gstack upgrades across global git, vendored, and local installs.

1|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/a29paul/hexlens --skill gstack-upgrade-a29paul
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gstack-upgrade
Source: https://github.com/a29paul/hexlens/tree/main/.claude/skills/gstack/gstack-upgrade
Command: npx skills add https://github.com/a29paul/hexlens --skill gstack-upgrade-a29paul

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the manual effort and risk of errors when updating gstack across different install types (global git, vendored, local project copies), managing auto-upgrade preferences, and running post-upgrade migrations to fix state and directory structure issues.

Core Features & Use Cases

  • Multi-install type support: Automatically detects and upgrades global git, vendored, and local project gstack installs without manual configuration.
  • Flexible update preferences: Lets users enable automatic upgrades, snooze reminders with escalating backoff (24h → 48h → 1 week), or disable update checks entirely.
  • Vendored copy sync: Automatically updates local vendored gstack copies to match the global install, or removes stale copies when team mode is active to avoid version conflicts.
  • Safe upgrade process: Creates backups before modifying installs, restores previous versions if setup fails, and runs idempotent version-specific migrations to fix state issues after upgrades.
  • Use Case: If you use gstack across multiple personal or team projects, this Skill ensures all your installs stay up to date without manual git pulls, file copies, or migration work.

Quick Start

Use the gstack-upgrade skill to upgrade your gstack installation to the latest version, sync any local vendored copies, and view the latest changelog.

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 across multiple install locations without manual git pulls?

The gstack-upgrade process automates updates across global git, vendored, and local project install types without manual git pulls. It detects each location, applies updates safely, and syncs versions to eliminate manual configuration.

How does vendored copy sync work when upgrading gstack?

Vendored copy sync automatically updates local gstack copies to match the global install version. In team mode, it removes stale copies to prevent version conflicts, keeping all environments consistent.

Can I configure automatic update preferences for gstack?

Yes, you can enable automatic upgrades, snooze reminders with escalating backoff from 24 hours to 1 week, or disable update checks entirely. This manages when and how gstack notifies you of new versions.

Is the gstack upgrade process safe if the setup fails?

The gstack upgrade process is safe because it creates backups before modifying installs and restores previous versions if setup fails. It also runs idempotent migrations to fix state issues post-upgrade.

What is the best way to manage gstack version migrations after an upgrade?

The best way to handle post-upgrade state and directory migrations is using the automatic idempotent migrations built into the gstack-upgrade process. These fix state issues safely without manual intervention.