What problem does it solve?
Manually keeping shared .claude and .mad configuration files consistent across multiple related repositories is time-consuming and prone to human error, leading to broken agent workflows and inconsistent rule sets across projects.
Core Features & Use Cases
- Config-driven sync pairs: Define repository pairs and sync rules in a single JSON config file, no skill code changes needed for new pairs.
- Safety-first operations: Built-in dry-run previews, conflict detection for diverged files, and project-specific pattern checks to prevent accidental overwrites of repo-specific content.
- Flexible sync control: Filter sync scope to specific file types (hooks, rules, skills etc.), reverse sync direction, and run post-sync verification commands to ensure target repo integrity.
Use case: Teams maintaining a core agent kit and multiple consumer projects can use this skill to automatically propagate updates to shared agent rules, hooks, and skills across all dependent repositories without manual file copying.
Quick Start
Use the repo-sync skill to preview and synchronize shared configuration files between your configured repository pairs after reviewing the dry-run output.