mzstack-upgrade

Upgrades mzstack installations via git or vendored methods with validation and changelog syncing.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/Ulanxx/mzstack --skill mzstack-upgrade
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mzstack-upgrade
Source: https://github.com/Ulanxx/mzstack/tree/main/mzstack-upgrade
Command: npx skills add https://github.com/Ulanxx/mzstack --skill mzstack-upgrade

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

mzstack upgrades can be brittle across diverse environments. This Skill automates detection of install type (global/local, git vendored), performs a safe upgrade, and keeps vendored copies in sync, reducing manual steps and downtime.

Core Features & Use Cases

  • Detects install type (global vs local; git vs vendored) and shows the appropriate upgrade path
  • Performs upgrade with safeguards (stashing local changes when needed, validating setup, and syncing vendored copies)
  • Provides a concise changelog of what's new after upgrade to help teams ship confidently

Quick Start

Run /mzstack-upgrade to check for updates and upgrade when available.

Frequently Asked Questions about mzstack-upgrade

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

FAQPage Schema
How do I upgrade mzstack to the latest version without losing local changes?

To upgrade mzstack safely, the skill detects your install type and automatically stashes local changes before applying the update, ensuring a clean install without overwriting your customizations.

What is the best way to automate mzstack version control across different environments?

Automating mzstack version control is handled by detecting whether you have a global, local, git-based, or vendored deployment, then applying the appropriate upgrade path to reduce manual steps and downtime.

Can I use this mzstack upgrade tool with a vendored deployment?

Yes, you can use this tool with vendored deployments. It performs the version upgrade and subsequently syncs the vendored copies to ensure all local mirrors match the latest installed release.

How does mzstack handle post-upgrade validation and changelog surfacing?

Post-upgrade validation confirms a clean install, and the skill presents a concise changelog of what's new, storing markers to help your team verify exactly what changed in the latest version.

Why does my mzstack upgrade break when switching between Git and vendored installs?

Upgrades can break across mixed environments due to mismanaged local changes. The tool prevents this by reading the current install type and applying safe git or vendored methods with proper stashing.