chief-upgrade

To upgrade Chief to the latest version, run /chief-upgrade to automatically detect your install type (global-git, local-git, or vendored), apply the upgrade, and display a What's New summary. It supports auto-upgrade, interactive prompts, and safe rollback for a seamless flow.

The safest way to automate version control updates for a vendored install is using an upgrade flow with built-in backup and restore capabilities. This ensures that if an upgrade fails, the system automatically rolls back to the previous state and syncs local vendored copies only after success.

Yes, you can rollback a failed upgrade. The upgrade process includes a safe rollback path that automatically restores your backup if the upgrade fails, ensuring your local-git or global-git installation remains intact and operational during version control updates.

Yes, the Chief upgrade process works with global-git, local-git, vendored, and vendored-global installations. It detects the specific install type, locates the correct install directory, and applies the appropriate upgrade flow with changelog parsing and post-upgrade synchronization for vendored copies.

To view the changelog and what's new after updating, the upgrade process parses the changelog and prints a concise What's New summary upon successful completion. This surfaces the latest changes immediately without requiring you to manually check separate version control logs.

Automated upgrade scripts for local software installs require a YAML frontmatter with a name and description in SKILL.md to function properly. If this structure is missing or the install directory cannot be detected, the reproducible upgrade flow will trigger clear error handling rather than proceeding blindly.