vibe-upgrade

Automate the official Vibe runtime upgrade workflow for Claude Code installations.

Updated May 9, 2026
One-click install
npx skills add https://github.com/kk20300113-png/my-claude-skills --skill vibe-upgrade-kk20300113-png
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vibe-upgrade
Source: https://github.com/kk20300113-png/my-claude-skills/tree/main/vibe-upgrade
Command: npx skills add https://github.com/kk20300113-png/my-claude-skills --skill vibe-upgrade-kk20300113-png

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the manual effort and potential routing conflicts of updating the Vibe runtime for Claude Code installations, ensuring you always run the latest official version with minimal hassle.

Core Features & Use Cases

  • Official Upgrade Workflow: Runs the canonical vgo-cli upgrade backend specifically for Claude Code, bypassing standard Vibe task routing to avoid unintended workflow triggers.
  • State Verification: Confirms the before and after installation state to validate that the upgrade completed successfully.
  • Use Case: If you are a developer using Claude Code with the Vibe runtime, use this Skill to get the latest official bug fixes and features without manually executing upgrade commands or troubleshooting routing errors.

Quick Start

Use the vibe-upgrade skill to update your current Claude Code Vibe runtime to the latest official version.

Frequently Asked Questions about vibe-upgrade

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

FAQPage Schema
How do I upgrade the Vibe runtime for Claude Code automatically?

To upgrade the Vibe runtime for Claude Code automatically, you can use a workflow that executes the vgo-cli upgrade backend, bypassing standard task routing to avoid triggering unintended workflows while applying the latest official version.

Why does my Vibe runtime upgrade trigger unintended workflow errors?

Standard Vibe task routing can trigger unintended workflow errors during an upgrade because it intercepts the update process. Bypassing this standard routing and directly executing the vgo-cli upgrade backend avoids these routing conflicts.

How does the Vibe runtime upgrade process validate installation states?

The Vibe runtime upgrade process validates installation states by checking the environment both before and after applying the update. This pre and post-installation state verification confirms that the vgo-cli backend successfully completed the runtime upgrade.

Can I update my Claude Code Vibe runtime without manual command execution?

Yes, you can update your Claude Code Vibe runtime without manual command execution by automating the official upgrade workflow. This approach runs the canonical vgo-cli backend directly, eliminating the need to manually type update commands.

What happens if the Vibe runtime upgrade fails on Claude Code?

If the Vibe runtime upgrade fails, the automated workflow reports precise backend errors returned by the vgo-cli. This precise error reporting helps developers identify exactly why the installation state validation or update process failed.