-
Notifications
You must be signed in to change notification settings - Fork 8k
Open
Description
Problem
Currently, skills installed in OpenCode (via git clone or manual copy) have no update mechanism:
- No update notification - Users don't know when upstream skills have new versions
- No auto-update - Must manually
git pullor re-clone each skill - No version tracking - No way to see installed vs latest version
This is especially problematic for popular skills like:
obra/superpowers(currently at v4.0.3)OthmanAdi/planning-with-files(currently at v2.4.1)nextlevelbuilder/ui-ux-pro-max-skill
Proposed Solution
Option A: Update Check Command
opencode skill check-updates
# Output:
# superpowers: v4.0.1 → v4.0.3 (update available)
# planning-with-files: v2.4.1 (up to date)Option B: Startup Notification
On startup, check for updates and show notification:
[!] 2 skill updates available. Run `/skill update` to update.
Option C: Auto-Update (with config flag)
// opencode.json
{
"skill": {
"autoUpdate": true, // or "notify" or false
"checkInterval": "daily"
}
}Implementation Considerations
- Skills installed via git clone can use
git fetchto check for updates - Skills from npm plugins would follow npm update mechanism (per PR feat(plugin): add skill support for plugins #9010)
- Need to track installation source (git URL vs manual copy vs npm)
Related Issues
- [FEATURE]: Skill Registry + Installer for Awesome-Claude-Skills (Make OpenCode the One Tool) #8386 - Skill Registry proposal (includes version management)
- feat(plugin): add skill support for plugins #9010 - Plugin skill support (npm-based updates)
- [FEATURE]: Add Skill Configuration to Config Type #6013 - Add Skill Configuration to Config Type
Environment
- OpenCode v1.1.28
- Skills installed via git clone to
~/.config/opencode/skills/
Metadata
Metadata
Assignees
Labels
No labels