What is dot-gitlab-sync?

A template-based issue-writing tool for GitHub and GitLab, which are services used to track bugs, feature requests, and other development work. It creates issues that follow the repository's required format.

Use it to draft bug reports, feature requests, technical-debt tasks, and other GitHub issues or GitLab issues.

It prevents incomplete or inconsistently formatted issue reports. Repository templates provide the expected sections and project-specific conventions.

dot-gitlab-sync — Skill for Claude Code and Codex by KemingHe

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add KemingHe/common-devx --skill dot-gitlab-sync

Clone the repo

git clone --depth 1 https://github.com/KemingHe/common-devx

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/keminghe/common-devx/dot-gitlab-sync/github.svg)](https://agentmods.dev/skills/keminghe/common-devx/dot-gitlab-sync)

Your own site

<a href="https://agentmods.dev/skills/keminghe/common-devx/dot-gitlab-sync"><img src="https://agentmods.dev/badge/skills/keminghe/common-devx/dot-gitlab-sync/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/keminghe/common-devx/dot-gitlab-sync"><img src="https://agentmods.dev/badge/skills/keminghe/common-devx/dot-gitlab-sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 64 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,343 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00064	$0.01343
Opus 5.5	$0.00026	$0.00537
Sonnet 5.5	$0.00013	$0.00269
Haiku 4.5	$0.00006	$0.00134

Measured 1mo ago against content hash 083948d3794d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

dot-gitlab-sync scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/skills/dot-gitlab-sync/SKILL.md · 102 lines

How it starts

The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.

GitHub-GitLab Template Sync

Synchronize .github/ and .gitlab/ template directories, applying all necessary platform-specific transformations so both directories stay consistent.

Temporary persona: Senior DevOps engineer with expertise in cross-platform template management and CI/CD conventions.

When to Use This Skill

After editing issue or PR templates in .github/ and needing .gitlab/ updated
After editing issue or MR templates in .gitlab/ and needing .github/ updated
Auditing both directories for consistency after any template change
Setting up .gitlab/ templates for the first time from existing .github/ templates

Asset Resolution

Check ./assets/transformation-rules.md for the platform transformation reference
If not found, search **/transformation-rules.md in repository
If still not found, use the rules documented in this skill's Process section

Process

Step 1: Determine Sync Direction

Ask the user:

Source: Which directory was just edited? (.github/ or .gitlab/)
Target: Which directory needs updating?
If unclear, compare file modification timestamps to suggest a direction

Step 2: Inventory Templates

List templates in both directories:

.github/ISSUE_TEMPLATE/ vs .gitlab/issue_templates/
.github/pull_request_template.md vs .gitlab/merge_request_templates/merge_request_template.md
.github/ISSUE_TEMPLATE/config.yml (GitHub-only, no GitLab equivalent)

Report any templates that exist in source but not in target (new templates to create) or vice versa (orphaned templates to flag).

Step 3: Apply Transformations

For each template, apply the platform-specific transformations from the asset reference:

GitHub to GitLab:

Remove YAML frontmatter (name, about, title, labels fields)
Replace "PR" with "MR" and "pull request" with "merge request" in template body
Replace "issue/PR number" with "issue/MR number" in Related sections
Copy to GitLab directory structure (lowercase issue_templates/, merge_request_templates/)
Skip config.yml (no GitLab equivalent)

Read the full file on GitHub · 102 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago First seen · 102 lines · 64 tokens per session scan A 083948d3794d

Subscribe to this mod's changes

dot-gitlab-sync is a skill published in the GitHub repository KemingHe/common-devx (10 stars, last pushed 4mo ago), licensed MIT. It adds 64 tokens to every session and 1,343 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Claude Code Git and workflow agent-skills agentskills-io conventional-commits developer-experience documentation

han-release

Cut a Han release: update CHANGELOG.md with the changes since the last release, bump and tag every plugin that changed as {plugin-name}--v{version} so a version-constrained dependency can resolve, and publish a GitHub release crediting every merged pull request and closed issue to the people behind it. Use when…

testdouble/han · 172 tokens

han-update-documentation

Update Han plugin documentation so every skill, agent, guidance doc, index, and cross-reference is current and accurate. On a non-default branch, scopes the pass to entities the branch actually touched. On the default branch, performs a full documentation sweep across the whole plugin. Use when updating, refreshing…

testdouble/han · 167 tokens

git-workflow

Use when naming or scoping a branch, writing or fixing a commit message, picking the gitmoji for a commit, untangling history (rebase versus merge versus squash), or cutting a versioned release — the portable git-convention layer for any repo. Covers gitmoji + Conventional Commits, SemVer tags, branch hygiene…

ericrisco/rsc-harness · 127 tokens

dot-gitlab-sync