repo-mirror

Mirror cockpit content to multiple target repositories with rsync.

3|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/theomonfort/theomonfort --skill repo-mirror
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-mirror
Source: https://github.com/theomonfort/theomonfort/tree/main/.github/skills/repo-mirror
Command: npx skills add https://github.com/theomonfort/theomonfort --skill repo-mirror

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Mirror selected content from cockpit to multiple target repos, excluding private folders. Performs a full sync — files removed from cockpit are also removed from targets.

Core Features & Use Cases

  • Mirror content from cockpit to configured target repositories
  • Exclude private folders and sensitive data from syncing
  • Full synchronization: deletions in cockpit are propagated to targets to maintain parity

Quick Start

Run the mirror script to sync cockpit content to all configured target repositories.

Frequently Asked Questions about repo-mirror

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

FAQPage Schema
How do I mirror a git repository to multiple target repos?

To mirror a git repository to multiple target repos, run the mirror script to sync selected content from cockpit to all configured targets. It uses rsync to perform a full sync, ensuring files removed from the source are also deleted from targets.

Does rsync full synchronization delete files removed from the source repository?

Yes, rsync full synchronization deletes files removed from the source repository. This mirror propagates deletions from cockpit to all target repositories, maintaining strict parity between the source content and the synced targets.

Can I exclude private folders when syncing content to GitHub repositories?

Yes, you can exclude private folders when syncing content to GitHub repositories. The mirror enforces exclusions for private folders and sensitive data, ensuring they are not copied to any of the configured target repositories.

What is the best way to keep scripts and knowledge bases in sync across GitHub repos?

The best way to keep scripts and knowledge bases in sync across GitHub repos is using an automated rsync-based mirror. It clones configured targets and pushes content updates, maintaining strict parity while excluding private folders.

What happens to existing target repository files during a full rsync mirror?

During a full rsync mirror, existing target repository files are overwritten by cockpit content. Files removed from the source are also deleted from targets to maintain exact parity, while private folders remain excluded.