self-upgrade
# self-upgrade This Claude Code skill automates the Vellum assistant upgrade process by sequentially updating the vellum package to its latest version, verifying the update, restarting the gateway to apply protocol changes, and restarting the assistant itself. Use this skill when you need to upgrade Vellum to the latest available version while ensuring all components properly reload the new code without manual intervention.
git clone --depth 1 https://github.com/vellum-ai/vellum-assistant /tmp/self-upgrade && cp -r /tmp/self-upgrade/skills/self-upgrade ~/.claude/skills/self-upgradeSKILL.md
You are performing a self-upgrade of the Vellum assistant. Follow these steps **in order**. Use the `bash` tool to run each command. Confirm each step succeeds before moving to the next. ## Step 1: Record the current version ```bash vellum --version ``` Save this value to report later. ## Step 2: Install the latest vellum ```bash bun install -g vellum@latest ``` After updating, verify the new version: ```bash vellum --version ``` ## Step 3: Restart the gateway If a gateway process is running, restart it so it picks up any protocol or dependency changes from the new version: ```bash pgrep -f 'vellum-gateway|gateway/src/index.ts' || echo "No gateway process found" ``` If a gateway PID is found, send it SIGTERM so it drains gracefully: ```bash pkill -TERM -f 'vellum-gateway|gateway/src/index.ts' ``` Then start the gateway again using whatever method the user's deployment uses (e.g. `bun run gateway/src/index.ts`, a systemd service, or a container orchestrator). If you are unsure how the gateway is deployed, ask the user. ## Step 4: Restart the assistant Use `vellum sleep` to stop the running assistant and gateway, then `vellum wake` to start them again from the updated binary: ```bash vellum sleep && vellum wake ``` Verify it is running: ```bash vellum ps ``` **Important:** This is the last step because the current assistant process is the one executing this conversation. After the restart, the new assistant takes over and this conversation ends gracefully. ## After Upgrade Report back to the user with: - The previous and new vellum version - Assistant status (running, PID) - Gateway status (restarted or not found) - Any errors encountered during the process
>
>
>
>
Check Vellum Assistant architecture and package boundaries. Use when editing imports, moving code, adding endpoints, touching assistant/gateway/client/skill boundaries, or reviewing architecture-sensitive changes.
Review Vellum Assistant code changes for correctness, repo-specific quality rules, security risks, and missing validation. Use when reviewing diffs, preparing a PR, finishing implementation work, or when the user asks for a code review, quality pass, or pre-merge check in this repository.
Guide Vellum Assistant feature flag changes and rollout hygiene. Use when adding, editing, reviewing, or documenting assistant feature flags, rollout-gated behavior, or platform flag follow-up work.
Validate Vellum Assistant database and workspace migrations. Use when adding, editing, reviewing, or testing migrations, release-note migrations, persisted schemas, workspace file formats, or data backfills.