skills.rest
z3z1ma
z3z1maCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

sync-distributed-opencode-plugin

Monitors plugin filesystem changes and triggers rebuilds of dependent modules.

21|1|Updated Jan 31, 2026
Search Tags:#consistency#plugin#diff#distribution#sync#opencode
One-click install
npx skills add https://github.com/z3z1ma/agent-loom --skill sync-distributed-opencode-plugin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sync-distributed-opencode-plugin
Source: https://github.com/z3z1ma/agent-loom/tree/main/.opencode/skills/sync-distributed-opencode-plugin
Command: npx skills add https://github.com/z3z1ma/agent-loom --skill sync-distributed-opencode-plugin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures that the plugin file in the development copy (.opencode/plugins/.ts) and the shipped copy under src/agent_loom/**/opencode/plugins/.ts stay perfectly identical, preventing drift that causes inconsistencies across environments.

Core Features & Use Cases

  • Detects differences between the two plugin locations and reports divergences.
  • Applies synchronized changes to both copies to maintain byte-for-byte identity.
  • Use case: when updating a plugin in development, automatically propagate and verify the same change in the shipped path to avoid runtime mismatches.

Quick Start

Diff the two copies and apply identical changes to both to maintain byte-for-byte identity.

Frequently Asked Questions about sync-distributed-opencode-plugin

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

FAQPage Schema
How do I keep distributed plugin files in sync across development and shipped paths?▼

To keep distributed plugin files in sync, you diff the development copy in .opencode/plugins/* against the shipped copy in src/agent_loom/**/opencode/plugins/*, then apply identical changes to both to maintain byte-for-byte identity.

Why does my Opencode plugin behave differently in runtime than in development?▼

Runtime mismatches in Opencode plugins happen when the development copy under .opencode/plugins/* drifts from the shipped copy under src/agent_loom/**/opencode/plugins/*. Synchronizing both paths eliminates this drift.

What's the best way to eliminate drift between duplicate plugin files in a repository?▼

The best way to eliminate drift between duplicate plugin files is enforcing deterministic synchronization by requiring identical changes to both copies and adding regression checks to verify byte-for-byte identity before release.

How do I detect and report differences between two copies of a plugin file?▼

To detect and report differences between two copies of a plugin file, you diff the development path against the shipped path to identify divergences, then propagate updates to ensure both files mirror each other exactly.

Do I need any external dependencies to synchronize distributed Opencode plugins?▼

No external dependencies are required to synchronize distributed Opencode plugins. The process applies directly to the plugin files existing in the two specified locations within the repository.

When should I run a synchronization check on my distributed plugin copies?▼

You should run a synchronization check on distributed plugin copies before release to verify byte-for-byte identity, ensuring updates are mirrored and preventing runtime inconsistencies across environments.

Related Skills

Explore More Software Engineering Skills→
different-aidifferent-ai
63

plugin-creator

Create and organize OpenCode plugins with SKILL.md frontmatter and load paths.

Official
Basic
BaneeishaqueBaneeishaque

folder-comparison

Compare two directories for content and structural identity using rclone and diff.

Community
Intermediate
vitaliytvvitaliytv

n-llm-patch

Generate self-contained markdown prompts for cross-agent code changes.

Community
Intermediate
vzcovzco
15

sync-plugin

Synchronize private plugin assets to a public repository with frontmatter validation.

Official
Intermediate