gstack-upgrade

Upgrade gstack installations across global, local, and vendored copies.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps gstack installations up to date across different install types and prevents manual mistakes by detecting whether gstack is installed as a global git, local git, or vendored copy, backing up existing installs, and applying a safe upgrade flow.

Core Features & Use Cases

  • Install detection: Automatically detects global-git, local-git, vendored, and vendored-global installs and resolves the correct upgrade directory.
  • Safe upgrade workflow: Stashes local changes for git installs, backs up vendored installs, runs setup, restores on failure, and clears caches and markers after completion.
  • Vendored sync & changelog summary: Optionally synchronizes local vendored copies with the primary install and summarizes changelog entries between old and new versions into a concise user-facing list.
  • Use Case: Ideal for developers or CI maintainers who need to keep developer tooling consistent across machines, update vendored skill copies, or enable auto-upgrades with safe rollbacks.

Quick Start

Ask the assistant to run gstack-upgrade to detect your installation, perform a safe update, and summarize what's new.

Frequently Asked Questions about gstack-upgrade

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

FAQPage Schema
How do I safely upgrade a vendored git installation without losing local changes?

This tool detects your gstack install type, stashes local changes, and creates backups before running the upgrade. It restores the backup automatically if the upgrade fails, ensuring your local modifications are never lost.

What is the best way to automate gstack update checks across different install types?

Automating gstack update checks is handled by detecting global-git, local-git, and vendored installs. The process resolves the correct upgrade directory, runs setup, synchronizes vendored copies, and clears caches and markers after completion.

How does the changelog summary work when upgrading gstack versions?

The changelog summary extracts entries between your old and new gstack versions. It compiles the git changelog differences into a concise, user-facing list so you can quickly review what changed during the upgrade.

Can I synchronize local vendored copies with a primary global install?

Yes, you can synchronize local vendored copies with the primary install. During the upgrade workflow, the tool optionally syncs these vendored copies to keep developer tooling consistent across different machines and environments.

Does the gstack upgrade process support automatic rollback on failure?

Yes, the gstack upgrade supports automatic rollback on failure. After backing up the existing installation and running setup, the workflow restores the backup automatically if any part of the update process fails.

Why do I need to clear caches and markers after updating a vendored install?

Clearing caches and markers after updating a vendored install prevents stale state from causing conflicts. The upgrade workflow removes these automatically once the new version is successfully installed and synchronized.