gstack-upgrade

Automate gstack CLI upgrades across global, vendored, and local installations.

3|14|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/cegit27/moodle-proctor --skill gstack-upgrade-cegit27
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gstack-upgrade
Source: https://github.com/cegit27/moodle-proctor/tree/main/.claude/skills/gstack/gstack-upgrade
Command: npx skills add https://github.com/cegit27/moodle-proctor --skill gstack-upgrade-cegit27

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually updating the gstack CLI tool requires checking for new versions, handling different installation types (global, vendored, local), syncing local copies, and reviewing changelogs, which is time-consuming and prone to errors.

Core Features & Use Cases

  • Multi-install type support: Automatically detects and upgrades global git, vendored, and local gstack installations without manual path configuration.
  • Smart upgrade flow: Supports auto-upgrade, snooze reminders with escalating backoff, and team mode handling for shared repositories.
  • Post-upgrade maintenance: Runs version migrations to fix stale configs and syncs local vendored copies to match the primary global install.
  • Use Case: If you rely on gstack for workflow automation across your team, this skill ensures all installations stay up to date with the latest features and bug fixes without manual intervention.

Quick Start

Use the gstack-upgrade skill to update your gstack installation to the latest version and view a summary of recent changes.

Frequently Asked Questions about gstack-upgrade

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

FAQPage Schema
How do I upgrade the gstack CLI to the latest version?

Upgrading the gstack CLI is automated by detecting your installation type, checking for new versions, and applying the upgrade with your consent. This eliminates manual git operations and configuration updates.

How does gstack handle version migrations after an upgrade?

Post-upgrade version migrations run automatically to fix stale configurations and sync local vendored copies. This ensures your gstack installation matches the primary global install without manual intervention.

Can I automate gstack updates across different installation types?

Yes, the upgrade process supports global git, vendored, and local gstack installations. It automatically detects the install type and applies the correct upgrade path without requiring manual configuration.

What is the best way to manage gstack updates for a shared team repository?

Using team mode handling during the upgrade process ensures shared repositories stay synchronized. It manages snooze reminders with escalating backoff and syncs local copies to match the global install.

Why does upgrading gstack manually cause configuration errors?

Manual upgrades often miss syncing local vendored copies or running necessary version migrations, leading to stale configs. Automating the process handles these steps to prevent configuration drift.

Does the gstack upgrade process include changelog review?

Yes, the automated upgrade flow includes viewing a summary of recent changes. This provides changelog insights so you understand new features and bug fixes without manually reviewing release notes.