sync-guidelines

Coordinate cross-repo synchronization of guidelines, skills, and tools with drift detection.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/michael-conrad/.opencode --skill sync-guidelines
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-guidelines
Source: https://github.com/michael-conrad/.opencode/tree/main/skills/sync-guidelines
Command: npx skills add https://github.com/michael-conrad/.opencode --skill sync-guidelines

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating guidelines, skills, and tools across multiple repositories is error-prone and time-consuming. This skill provides an automated, AI-guided framework to keep content consistent, detect drift, and apply validated changes without breaking projects.

Core Features & Use Cases

  • Cross-repo synchronization of guidelines, skills, and tools using a centralized orchestrator.
  • Drift detection and alignment by comparing source and target repos and proposing reconciliations.
  • Content governance with clear core vs project-specific classification to avoid destructive syncs.
  • Sub-agent orchestration that delegates diff analysis, decision making, and change propagation to specialized workers.
  • Worktree-mode readiness to operate safely in a live repository context.

Quick Start

Prompt the AI to begin a cross-repo synchronization of guidelines, skills, and tools.

Frequently Asked Questions about sync-guidelines

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

FAQPage Schema
How do I synchronize guidelines and tools across multiple repositories automatically?

Drift detection compares source and target repositories to identify misalignments in guidelines, skills, and tools, then proposes reconciliations and applies validated changes without breaking existing projects.

What is the best way to detect content drift between repositories?

Drift detection in repository synchronization compares source and target repos to identify misaligned content, then proposes reconciliations and dispatches sub-agents to apply validated changes without breaking projects.

How do I prevent destructive synchronization from overwriting project-specific repository content?

To prevent destructive synchronization, content governance classifies assets as either core or project-specific, ensuring the orchestrator only applies validated changes to shared assets while preserving localized project configurations.

Can I run cross-repo synchronization directly within a live repository worktree?

Yes, cross-repo synchronization supports worktree-mode readiness, allowing the AI orchestrator and sub-agents to operate safely and apply content changes directly within a live repository context.

How do sub-agents handle diff analysis during cross-repo synchronization?

Sub-agents handle diff analysis during cross-repo synchronization by receiving dispatched tasks from the orchestrator to evaluate guideline drift, make change decisions, and propagate updates across target repositories with recorded provenance.