repo-sync

Synchronize shared .claude and .mad config files between paired repositories.

Updated May 7, 2026
One-click install
npx skills add https://github.com/tmalcolm-0607/mad-council-claw --skill repo-sync-tmalcolm-0607
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-sync
Source: https://github.com/tmalcolm-0607/mad-council-claw/tree/main/.claude/skills/repo-sync
Command: npx skills add https://github.com/tmalcolm-0607/mad-council-claw --skill repo-sync-tmalcolm-0607

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about repo-sync

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

FAQPage Schema
How do I sync shared .claude configuration files across multiple repositories?

To sync shared .claude configuration files across multiple repositories, define repository pairs and sync rules in a JSON config file. This eliminates manual copy-paste errors and ensures consistent agent rules, hooks, and skills across all related project repositories.

What is the best way to prevent copy-paste errors when updating cross-repo agent rules?

The best way to prevent copy-paste errors when updating cross-repo agent rules is using config-driven sync pairs with built-in conflict detection. This automatically propagates updates to shared rules across dependent repositories while detecting diverged files.

Can I preview configuration file changes before applying them to a target repository?

Yes, you can preview configuration file changes before applying them using the built-in dry-run preview feature. This safety-first operation shows exactly what will be synchronized across your repository pairs before any files are modified.

How do I limit config sync scope to specific file types like hooks or skills?

You can limit config sync scope to specific file types like hooks or skills using flexible sync control filters. This allows you to target only the necessary configuration assets while preserving repository-specific content during synchronization.

What happens when configuration files have diverged across paired repositories?

When configuration files have diverged across paired repositories, the conflict detection feature identifies the differences and prevents accidental overwrites. Project-specific pattern checks ensure repo-specific content remains intact during synchronization.