check-skill-updates

Detect upstream changes and apply updates to imported OpenCode skills.

5|Updated Jan 14, 2025
One-click install
npx skills add https://github.com/timmo001/dotfiles --skill check-skill-updates
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-skill-updates
Source: https://github.com/timmo001/dotfiles/tree/main/agents/.config/opencode/skills/check-skill-updates
Command: npx skills add https://github.com/timmo001/dotfiles --skill check-skill-updates

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps users monitor and apply updates to externally imported OpenCode skills by comparing local files with their upstream repositories, ensuring they stay current.

Core Features & Use Cases

  • Upstream Change Detection: Checks for new commits or modifications in skills' upstream repositories to identify available updates.
  • Diff Review & Application: Compares local and upstream versions, allowing users to review differences and selectively apply changes.
  • Use Case: A developer maintains a collection of imported skills and wants to periodically ensure they incorporate latest improvements without overwriting local customizations.

Quick Start

Run the check command to see if any upstream skills have updates pending, then decide whether to review or apply them directly.

Frequently Asked Questions about check-skill-updates

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

FAQPage Schema
How do I track upstream changes for imported Git repository skills?

Track imported Git repository skills by detecting upstream changes through commit SHAs, allowing you to compare local files with their source repositories and identify available updates.

What is the best way to update imported skills without overwriting local customizations?

Update imported skills without losing local customizations by comparing local and upstream versions with a diff, then selectively applying only the desired changes from the source repository.

How does Git commit SHA comparison work for synchronizing skill collections?

Git commit SHA comparison synchronizes skill collections by checking local SHAs against upstream repository commits to detect modifications and apply pending updates accurately across environments.

Can I review the diff between local and upstream skill versions before applying updates?

Yes, you can review the diff between local and upstream skill versions before applying updates, allowing you to evaluate differences and decide whether to incorporate the latest improvements directly.

Do I need Git installed to monitor and apply updates to imported skills?

Yes, Git is required to monitor and apply updates to imported skills, because the process relies on Git operations and diff comparison logic within the script to detect upstream changes.

Why are my imported OpenCode skills not showing pending updates from the upstream repository?

Imported OpenCode skills may not show pending updates if local commit SHAs already match the upstream repository, meaning your local files are fully synchronized with the latest upstream changes.