Verified:GitHub

dot-gitlab-sync

Synchronize GitHub and GitLab repository issue and PR/MR templates.

9|1|Updated Jul 9, 2025

Search Tags:#devops #templates #github #sync #gitlab #frontmatter #terminology

One-click install

npx skills add https://github.com/KemingHe/common-devx --skill dot-gitlab-sync

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: dot-gitlab-sync
Source: https://github.com/KemingHe/common-devx/tree/main/.agents/skills/dot-gitlab-sync
Command: npx skills add https://github.com/KemingHe/common-devx --skill dot-gitlab-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Synchronizes and reconciles repository issue and PR/MR templates between GitHub and GitLab so teams do not need to manually convert formats, rename files, or hunt down inconsistent terminology across platforms.

Core Features & Use Cases

Inventory templates in .github/ and .gitlab/ and report missing or orphaned files.
Apply platform-specific transformations such as removing or adding YAML frontmatter, mapping directory names and casing, and replacing PR/MR terminology.
Validate post-sync consistency by checking template bodies, frontmatter presence, and residual terminology.
Use cases: initialize GitLab templates from an existing GitHub set, keep both template directories consistent after edits, and audit repositories for template drift.

Quick Start

Ask the agent to "Sync my .github templates to .gitlab and apply the skill's platform transformation rules."

Frequently Asked Questions about dot-gitlab-sync

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

FAQPage Schema

How do I sync issue and PR templates between GitHub and GitLab?▼

To sync issue and PR templates between GitHub and GitLab, you can inventory directories like .github and .gitlab, apply platform-specific frontmatter and terminology transformations, and validate consistency to eliminate manual format conversion and drift.

What's the best way to convert GitHub pull request templates for GitLab merge requests?▼

Converting GitHub pull request templates to GitLab merge requests involves mapping directory names, replacing PR terminology with MR terminology, and adjusting YAML frontmatter to match GitLab's platform-specific requirements while preserving the original template intent.

How do I audit repositories for template drift across GitHub and GitLab?▼

Auditing repositories for template drift requires inventorying template files in both .github and .gitlab directories, identifying missing or orphaned files, and validating post-sync consistency by checking template bodies and residual terminology.

Does synchronizing GitHub and GitLab templates require custom transformation rules?▼

Synchronizing GitHub and GitLab templates supports optional custom transformation rules via an assets/transformation-rules.md file, allowing teams to define specific terminology mappings and validation logic beyond the default frontmatter and directory casing transformations.

Can I initialize GitLab issue templates from an existing GitHub repository?▼

Initializing GitLab issue templates from an existing GitHub repository is possible by inventorying the .github template set, applying platform-specific frontmatter additions, and generating corresponding .gitlab files with consistent structure and terminology.

Why do my synced templates still show inconsistent terminology across platforms?▼

Inconsistent terminology after syncing templates usually indicates missing transformation rules or incomplete terminology mapping, which can be resolved by validating residual terminology and applying custom rules via assets/transformation-rules.md.