gstack-upgrade

Upgrade gstack installations and resolve version drift across global, local, and vendored copies.

20|3|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/Walrus-Computing/piper-draw --skill gstack-upgrade-walrus-computing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gstack-upgrade
Source: https://github.com/Walrus-Computing/piper-draw/tree/main/.claude/skills/gstack/gstack-upgrade
Command: npx skills add https://github.com/Walrus-Computing/piper-draw --skill gstack-upgrade-walrus-computing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill upgrades gstack safely across different installation layouts, preventing version drift and reducing manual maintenance.

Core Features & Use Cases

  • Install Detection: Identifies whether gstack is installed globally, locally, or as a vendored copy.
  • Safe Upgrade Flow: Runs the right upgrade path, preserves local changes when needed, and restores cleanly if a step fails.
  • Post-Upgrade Maintenance: Applies version migrations and refreshes stale vendored copies so all installs stay aligned.
  • Change Summary: Reviews the changelog and presents a concise summary of what changed after the upgrade.
  • Use Case: Ask for an update when your gstack install is outdated, partially migrated, or needs to be synchronized across a team workspace.

Quick Start

Ask the skill to upgrade gstack to the latest version and summarize the changes after the upgrade.

Frequently Asked Questions about gstack-upgrade

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

FAQPage Schema
How do I upgrade a vendored install to the latest version safely?

Upgrading a vendored install safely involves detecting your installation layout, running the appropriate upgrade path, preserving local changes, and restoring cleanly if a step fails. This resolves version drift and refreshes stale copies.

What is the best way to resolve install drift across a team workspace?

Resolving install drift across a team workspace requires synchronizing aligned copies. The upgrade process applies version migrations and refreshes stale vendored copies so every team installation stays aligned.

How does a safe upgrade flow handle failed migration steps?

A safe upgrade flow handles failed steps by utilizing safe fallback behavior. If a migration step fails, the process restores your environment cleanly to its previous state from the created backup.

Can I get a changelog summary after completing a version sync?

Yes, you can get a changelog summary after completing a version sync. The upgrade process reviews the changelog and presents a concise summary of what changed immediately after the update completes.

Does the upgrade process support global, local, and vendored installations?

Yes, the upgrade process supports global, local, and vendored installations. It identifies your specific installation layout and runs the correct upgrade path, including team-mode cleanup for synchronized copies.