repo-sync

Repo-sync is a specialized orchestration skill designed for the workspace-hub multi-repository architecture. It automates the complex task of keeping 25+ independent Git repositories synchronized, handling state anomalies that frequently occur in large-scale development environments. The agent performs a multi-phase operation: bulk pulling, failure diagnosis, automated remediation, encoding health verification, and background ecosystem health reporting. It is intended for software engineers and systems architects who manage distributed codebases and require a reliable, non-destructive way to recover from common Git synchronization issues such as detached HEADs, uncommitted changes, and diverged branch history.

• Executes bulk Git operations across all submodules and repositories using optimized scripts.

• Performs granular diagnosis for failure modes including diverged branches, dirty working trees (uncommitted changes), detached HEAD states, and missing upstream tracking branches.

• Applies surgical auto-fixes such as stashing dirty changes, merging diverged branches with the --no-rebase strategy, and resetting submodule pointers when appropriate.

• Includes a specialized encoding health check that identifies and flags Windows-originated UTF-16/CRLF files, ensuring repository cleanliness and preventing pipeline parsing errors.

• Triggers background ecosystem health audits via the ecosystem-health skill to maintain global system integrity without blocking user workflows.

• Implements rigorous safety protocols, including a 'read-only/archived' remote exception handler that preserves local-only commits as patch artifacts before alerting developers.

• Always defaults to merging rather than rebasing to maintain stable Git history across the workspace-hub ecosystem.

• Handles detached HEAD states for submodules (e.g., digitalmodel and worldenergydata) as intended behavior, preserving pinned commit integrity.

• Provides a structured markdown summary table post-execution detailing the repo name, detected issue, applied fix, and the final outcome.

• Requires local write permissions and operates by invoking standard Git binaries and shell scripts within the repository workspace.

• Does not force-push or reset hard unless explicitly triggered, prioritizing data safety and manual human verification for destructive scenarios like conflicting stashes.