sync-all-repos

Name: sync-all-repos
Availability: InStock
Author: luiseiman

Discover and synchronize GitHub-backed repositories across machines with safe auto-actions.

8|1|Updated Mar 19, 2026

Search Tags:#automation #git #github #reporting #sync #repos

Ready to run

npx skills add https://github.com/luiseiman/dotforge --skill sync-all-repos

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sync-all-repos
Source: https://github.com/luiseiman/dotforge/tree/main/skills/sync-all-repos
Command: npx skills add https://github.com/luiseiman/dotforge --skill sync-all-repos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordination of multiple GitHub-backed repositories across machines is error-prone and time-consuming. sync-all-repos automates repo discovery, status classification, and safe auto-actions while surfacing ambiguous cases for Claude to resolve.

Core Features & Use Cases

Discover GitHub-backed repos on the host and classify each by sync state (in-sync, behind, ahead, diverged, dirty, non-main).
Auto-resolve simple states (pull behind, push ahead, rebase when safe) and report complex cases for human decision.
Provide a structured summary report and handle opt-out markers for ignored projects.

Quick Start

Ask me to scan your machine for GitHub-backed repos and generate a sync report.

Frequently Asked Questions about sync-all-repos

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

FAQPage Schema

How do I sync all my GitHub repositories across multiple machines automatically?▼

Yes, repository synchronization handles dirty working directories and non-main branches by detecting them during the scan and reporting them in the structured summary. It avoids auto-committing dirty states and skips them to prevent data loss or conflicts.

How does automated git synchronization handle diverged branches safely?▼

To set up automated repo synchronization, you need local machines or servers with multiple cloned GitHub repositories and up-to-date remotes. The process requires per-repo timeouts for fetch and status operations and explicit safety constraints configured before execution.

Can I exclude specific projects from the GitHub repo sync process?▼

Yes, you can exclude specific projects from the GitHub repo sync process by using opt-out markers for ignored projects. The synchronization tool detects these markers during repository discovery and skips those worktrees, including non-GitHub or Claude-managed ones.

What are the limitations of automatically synchronizing multiple git repositories?▼

Limitations of automatic git repository synchronization include no force-push, no auto-commit for dirty directories, and skipping non-GitHub or Claude-managed worktrees. It also requires up-to-date remotes and per-repo timeouts to prevent hanging during fetch operations.