gl-gh-sync

Bidirectionally synchronize code between GitLab and GitHub repositories.

2.3k|237|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/AgentsMesh/AgentsMesh --skill gl-gh-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gl-gh-sync
Source: https://github.com/AgentsMesh/AgentsMesh/tree/main/.claude/skills/gl-gh-sync
Command: npx skills add https://github.com/AgentsMesh/AgentsMesh --skill gl-gh-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the bidirectional synchronization of code between GitLab and GitHub repositories, ensuring consistency across both platforms and streamlining development workflows.

Core Features & Use Cases

  • Automatic Direction Detection: Intelligently determines which repository has newer commits.
  • Fast-Forward Pushing: For simple linear history, it directly pushes changes without extra commits.
  • PR/MR Workflow for Forks: Handles divergent histories by initiating Pull Requests (GitHub) or Merge Requests (GitLab) for manual review and merging.
  • Status Checking: Allows users to view differences between repositories without performing any synchronization.

Quick Start

Run the gl-gh-sync skill to automatically synchronize your GitLab and GitHub repositories.

Frequently Asked Questions about gl-gh-sync

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

FAQPage Schema
How do I sync code between a GitLab and GitHub repository?

Bidirectional sync between GitLab and GitHub works by automatically detecting which repository has newer commits and applying fast-forward pushes to align both codebases without creating extra merge commits.

What happens when GitLab and GitHub histories diverge during synchronization?

When GitLab and GitHub histories diverge, the sync process initiates Pull Requests on GitHub or Merge Requests on GitLab, allowing you to manually review and resolve differences before merging the code.

Can I check the difference between my GitLab and GitHub repos without syncing them?

Yes, you can check repository differences without executing synchronization by running a status check, which compares the commit histories of GitLab and GitHub and displays the variations without pushing any code.

How does automatic direction detection work for GitLab and GitHub syncing?

Automatic direction detection for GitLab and GitHub syncing intelligently evaluates commit timestamps across both repositories to determine which branch has the newest changes, then pushes those updates to the outdated repository.

Is fast-forward pushing supported for linear histories between GitHub and GitLab?

Fast-forward pushing is fully supported for simple linear histories, directly transferring commits between GitHub and GitLab to maintain a clean timeline without introducing unnecessary merge commits.