gstack-upgrade

Automate end-to-end gstack upgrades across global, vendored, and team installs.

Updated May 27, 2026
One-click install
npx skills add https://github.com/Shmurdoc/EasyRide-v1 --skill gstack-upgrade-shmurdoc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gstack-upgrade
Source: https://github.com/Shmurdoc/EasyRide-v1/tree/main/.opencode/skills/gstack-upgrade
Command: npx skills add https://github.com/Shmurdoc/EasyRide-v1 --skill gstack-upgrade-shmurdoc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Updating gstack across different installation setups (global git, vendored local, team mode environments) requires manual version checks, git command execution, and local copy synchronization, which is tedious and prone to errors. This Skill automates the entire process, removing the overhead of manual tool maintenance for developers.

Core Features & Use Cases

  • Automated Install Detection: Automatically identifies gstack's installation type and directory path, no manual path configuration required.
  • Flexible Update Controls: Supports auto-upgrades, snoozed reminders with escalating backoff, and manual approval prompts to align with user preferences.
  • Vendored Copy Management: Automatically updates or removes local vendored gstack copies based on team mode settings, preventing version conflicts across projects.
  • Use Case: Development teams using gstack across multiple repositories can use this Skill to ensure all environments run the latest version without individual developers running manual update commands.

Quick Start

Invoke the gstack-upgrade skill to automatically update gstack to its latest version, including detecting your install type, running the upgrade, and summarizing new features for you.

Frequently Asked Questions about gstack-upgrade

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

FAQPage Schema
How do I automate gstack upgrades across different installation types?

Automating gstack upgrades is handled by detecting the installation type and executing git-based updates automatically. This process identifies global git, vendored local, or team mode environments and runs post-update migrations without manual version tracking.

What is the best way to sync local vendored gstack copies during a team upgrade?

Syncing local vendored gstack copies is managed automatically based on team mode settings. The upgrade process updates or removes local copies to prevent version conflicts across project repositories.

Does the gstack upgrade process support snoozing update reminders?

Update reminders support snoozing with escalating backoff logic. The upgrade process offers flexible controls including auto-upgrades, snoozed reminders, and manual approval prompts to align with developer preferences.

How to view changelog summaries after updating gstack?

Changelog summaries are delivered automatically upon completing the gstack upgrade. The process executes the git-based version update and then provides a user-facing summary of new features without requiring manual changelog checks.

Can I use automated tool maintenance for gstack without manual path configuration?

Automated tool maintenance for gstack requires no manual path configuration. The process automatically detects the installation directory path, identifying the correct setup type to execute updates seamlessly.

Why does gstack version management fail across multiple repositories?

Version management fails when local vendored copies diverge from the main gstack version. Automating the upgrade process synchronizes these copies and runs necessary migrations to ensure consistency across all environments.