oh-my-opencode-update

Upgrade, reinstall, and troubleshoot the oh-my-opencode plugin with backup and verification.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/canyangliunian/Agent-skills --skill oh-my-opencode-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oh-my-opencode-update
Source: https://github.com/canyangliunian/Agent-skills/tree/main/oh-my-opencode-update
Command: npx skills add https://github.com/canyangliunian/Agent-skills --skill oh-my-opencode-update

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bun, oh-my-opencode, opencode, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Use when upgrading, reinstalling, or troubleshooting the oh-my-opencode plugin for opencode (OpenCode), especially when old caches/lockfiles/permissions cause the new version not to take effect; supports upgrading to latest or a pinned version with backup and verification.

Core Features & Use Cases

  • Upgrades to latest by default, with support for a pinned version.
  • Backs up existing config files, clears caches, and performs a graceful reinstall.
  • Verifies installation and health post-update, with safety stops on critical failures.

Quick Start

From the skill root, run the update script in dry-run mode to preview upgrading to the latest version.

Frequently Asked Questions about oh-my-opencode-update

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

FAQPage Schema
How do I safely upgrade the oh-my-opencode plugin when old caches prevent the new version from taking effect?

To safely upgrade oh-my-opencode, this skill automates backing up existing configs, clearing caches and lockfiles, and verifying the new installation post-update. A dry-run option lets you preview the upgrade process before applying any changes.

What is the best way to reinstall an opencode plugin to a specific pinned version?

The best way to reinstall an opencode plugin to a pinned version is using an automated workflow that backs up config files, clears caches, and installs the target version. This ensures the specified version takes effect cleanly without residual lockfile conflicts.

Why does my oh-my-opencode upgrade fail due to permission issues and how can I fix it?

Upgrades fail due to permission issues when old caches or lockfiles block the new version. This skill fixes it by performing a graceful reinstall that clears caches, backs up configurations, and verifies installation health with safety stops on critical failures.

Does the oh-my-opencode update process support a dry-run before applying changes?

Yes, the oh-my-opencode update process supports a dry-run mode. You can run the update script from the skill root in dry-run to preview upgrading to the latest version without modifying your existing config files or clearing caches.

Can I restore my opencode config files if a plugin upgrade breaks my environment?

Yes, you can restore opencode config files because the upgrade workflow includes a backup and restore mechanism. It backs up existing config files before clearing caches and reinstalling, ensuring you can recover your environment if installation fails.