gstack-upgrade
by garrytangstack-upgrade is the skill for updating gstack safely. It detects global vs vendored installs, runs the upgrade path, and summarizes what changed so you can verify the result. Use this gstack-upgrade guide for install and usage details, migration-aware behavior, and workflow automation cases.
This skill scores 78/100, which means it is a solid listing candidate for directory users who want a targeted gstack upgrade workflow instead of improvising a generic prompt. The repository gives enough trigger language, operational branching, and migration logic to make installation decision-worthy, though it is not packaged with helper docs or an install command.
- Explicit trigger handling for "upgrade gstack" / "update gstack" plus voice aliases, so agents can invoke it with low guesswork.
- Operational flow is concrete: it detects auto-upgrade vs user confirmation, then restores from backup on failure and reports what changed.
- The repository includes multiple versioned migration scripts, showing real upgrade coverage beyond a placeholder instruction page.
- No install command, scripts, or reference docs are provided in the skill folder, so adopters must infer setup from the skill content itself.
- The long body is autogenerated and upgrade-focused; users needing broader gstack operations will need other skills or manual guidance.
Overview of gstack-upgrade skill
What gstack-upgrade does
gstack-upgrade is the skill you use when you want to update gstack itself, not just patch a single workflow step. It detects whether gstack was installed globally or in a vendored layout, runs the upgrade path, and then surfaces what changed so you can verify the result quickly. If you need a reliable gstack-upgrade guide for “update this tool without breaking my setup,” this is the right fit.
Who should install it
Install the gstack-upgrade skill if you maintain a gstack-based workflow, rely on Claude Code skills stored under ~/.claude/skills, or need upgrades to happen with less manual repo inspection. It is especially useful for users who want the skill to handle install-type differences automatically instead of guessing whether they should run a global or local upgrade.
Why it is different
The main value of gstack-upgrade for Workflow Automation is that it is upgrade-oriented rather than generic prompt-oriented. The skill is built around version-aware behavior, user confirmation, backup/restore logic, and migration scripts. That makes it more trustworthy than a one-shot “please update” prompt when the install has history, not just a clean state.
How to Use gstack-upgrade skill
Install and load context
Use the directory’s install command if your environment supports it, then let Claude Code load the skill by name. For this repository, the documented install pattern is:
npx skills add garrytan/gstack --skill gstack-upgrade
After installation, open SKILL.md first. Then read SKILL.md.tmpl and the migration scripts in migrations/ to understand the actual upgrade steps and the version-specific edge cases before you ask the skill to run.
Give the skill the right starting prompt
A good gstack-upgrade usage prompt is short but specific: “Upgrade gstack from the current installed version to the latest release and tell me if anything needs review.” If you already know the install shape, say so: “This is a vendored install under ~/.claude/skills; upgrade safely and preserve backups.”
Stronger inputs include:
- current version if known
- whether you want auto-upgrade behavior
- whether you need confirmation before changing files
- any constraints like offline work, limited shell access, or a custom skills path
Read these files first
For decision quality, preview the files that drive behavior, not just the landing page:
SKILL.mdfor the live upgrade flowSKILL.md.tmplfor the authored source of truthmigrations/v0.15.2.0.shfor directory-structure fixesmigrations/v1.0.0.0.shfor first-run prompt behaviormigrations/v1.1.3.0.shfor install cleanup logicmigrations/v1.17.0.0.shandmigrations/v1.27.0.0.shfor later rename and wireup changes
Practical workflow tips
Use the skill when you need an upgrade with verification, not when you only want a conceptual changelog. The most important input is whether the install is global, vendored, or mixed, because that affects which paths the skill should touch. If you are running in an environment with automated approvals, confirm whether GSTACK_AUTO_UPGRADE=1 or config-based auto-upgrade is already enabled before invoking the skill.
gstack-upgrade skill FAQ
Is gstack-upgrade only for upgrades?
Yes. The gstack-upgrade skill is scoped to moving gstack to a newer version and handling the follow-up work. It is not a general troubleshooting skill for unrelated repo tasks, and it is not meant to replace a custom migration plan for another project.
Do I need to be a beginner to use it?
No. Beginners can use it if they follow the install step and provide a plain request, but the best results come from users who can name their install type and risk tolerance. If you are unsure, ask for a normal upgrade with confirmation turned on.
How is it different from a normal prompt?
A normal prompt may ask an assistant to “upgrade gstack,” but gstack-upgrade encodes the versioned workflow, confirmation logic, and migration-aware behavior that make the upgrade safer. That matters when the install has historical migrations or when the skill needs to decide whether to ask first or auto-run.
When should I not use it?
Do not use gstack-upgrade if you only want to read release notes, if you are not actually running gstack, or if you need a broader system maintenance tool. It is also a poor fit if you want a fully manual review of every migration before any file change happens.
How to Improve gstack-upgrade skill
Give version and install details up front
The biggest quality gain comes from telling the skill what it is upgrading and where it lives. “Upgrade my global gstack install from v1.0 to latest” is better than “fix it,” because the skill can align the upgrade path with the install type and avoid unnecessary detection work.
State your tolerance for automation
If you want the gstack-upgrade skill to move quickly, say whether auto-upgrade is allowed. If you want review before changes, say that too. This reduces ambiguity around confirmation steps and helps the skill choose the safer branch when it encounters UPGRADE_AVAILABLE.
Watch for migration-sensitive cases
The main failure mode is assuming every install is clean. Older installs may need directory structure repair, resource-log migration, prompt-style changes, or repo rename handling. If your environment has any of those history markers, mention them in the request so the upgrade can verify them instead of rediscovering them late.
Iterate on the first result
After the first upgrade, check whether the new behavior matches your workflow: install location, confirmation style, and any changed prompt defaults. If something feels off, ask for a follow-up pass that only addresses the mismatch, such as “keep terse prose,” “restore prior upgrade confirmation behavior,” or “re-run with backup preserved.”