vf-update

Diagnoses VibeFlow plugin, module, and GSD engine versions before applying updates.

9|Updated May 24, 2026
One-click install
npx skills add https://github.com/picmakpro/vibeflow-os --skill vf-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vf-update
Source: https://github.com/picmakpro/vibeflow-os/tree/main/plugin/conductor/skills/vf-update
Command: npx skills add https://github.com/picmakpro/vibeflow-os --skill vf-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents risky or incomplete VibeFlow upgrades by diagnosing plugin, module, and GSD engine versions before applying changes.

Core Features & Use Cases

  • Version Diagnostics: Compare the installed VibeFlow plugin with the latest published release and detect legacy GSD engine states.
  • Controlled Updates: Present the changelog and request explicit human confirmation before updating the plugin or installed modules.
  • Migration Safety: Handle plugin failures, network uncertainty, module refreshes, and optional migration to the opengsd GSD core with independent confirmation.
  • Use Case: When a new VibeFlow release is available, use this Skill to review the changes, update the plugin cache and installed modules, and migrate the legacy engine only after approval.

Quick Start

Ask the vf-update skill to check for available VibeFlow updates and show the changelog before making any changes.

Frequently Asked Questions about vf-update

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

FAQPage Schema
How do I safely update the VibeFlow plugin without breaking installed modules?

To safely update the VibeFlow plugin, use a diagnostic workflow that compares installed versions against the latest release, presents the changelog for review, and requires explicit human confirmation before applying plugin upgrades or module updates.

What is VibeFlow module rematerialization and when do I need it?

VibeFlow module rematerialization is the process of refreshing installed modules during a plugin upgrade. You need it when a new VibeFlow release is available, ensuring installed modules stay compatible with the updated plugin cache and latest version diagnostics.

Can I check for available VibeFlow updates without applying changes?

Yes, you can run check-only diagnostics to compare your installed VibeFlow plugin with the latest published release. This scope detects available updates and legacy GSD engine states without applying any changes, allowing you to review the changelog first.

Does VibeFlow migration support moving from a legacy GSD engine to the opengsd core?

Yes, VibeFlow migration supports optionally moving from a legacy GSD engine to the opengsd GSD core. This engine migration requires independent human confirmation to ensure safety, handling network uncertainty and plugin failures during the transition process.

How do I update only specific VibeFlow modules without upgrading the core plugin?

You can use a modules-only scope to update installed VibeFlow modules independently without upgrading the core plugin. This targeted approach runs local diagnostic and update scripts while handling network uncertainty, ensuring safe module refreshes.

What happens if a VibeFlow plugin update fails due to network issues?

If a VibeFlow plugin update fails due to network issues, the update workflow uses best-effort network handling to manage the uncertainty. It diagnoses available releases and legacy engine states first, ensuring no risky or incomplete upgrades are applied.