Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →agentsmesh/github-gitlab-mirror
Audits or synchronizes the authoritative GitHub main branch to the internal GitLab mirror without importing GitLab-only history back into GitHub.
Passed 17 of 21 test cases with the skill, and 11 of 21 without it.
and 4 more in the full report
7 fixed11 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
After pushing to GitLab, we re-fetched both remotes and discovered GitHub main received a new commit while we were syncing. Is the synchronization complete?
| Checked | Without skill | With skill |
|---|---|---|
| Loops back to the status evaluation phase to mirror the newest GitHub commit | Missed | Passed |
The instructions your model reads when the skill loads.
GitHub main is the single source of truth. GitLab exists to build and deploy
the same commit internally.
origin
and gitlab.--force-with-lease expectation.Fetch both authoritative refs:
git remote -v
git fetch <github-remote> main
git fetch <gitlab-remote> main
Record both SHAs and show commits unique to either side:
git rev-parse <github-remote>/main
git rev-parse <gitlab-remote>/main
git log --oneline <gitlab-remote>/main..<github-remote>/main
git log --oneline <github-remote>/main..<gitlab-remote>/main
Classify the relationship:
test cases passed, vs 11 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.