sync-branch SKILL.md skillB
sync-branch from vzakharov/muthur is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add vzakharov/muthur/sync-branch@git:20261016.bb62c02Pins git:20261016.bb62c02 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- vzakharov/muthur
- Path
.claude/skills/sync-branch/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261016.bb62c02, committed Oct 16, 2026
- First version recorded
- Aug 8, 2026
- Size
- 10,005 bytes
- Repository stars
- 22
- License
- MIT
Bring a branch up to date with its merge target — merge it in with the conflicts committed as git left them, resolve them in a commit of their own, then push, so the resolution reviews on GitHub as an ordinary commit. Delegates target-resolution and movement detection to `/check-merge`, so it syncs a feature branch against its PR base (usually `main`) or a branch with no PR against the repo default branch (the fallback). Invoke as `/sync-branch [<branch>] [no vet]`. Use when the user says…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
`/sync-branch` reconciles a branch with its **merge target** — the branch its PR is based on — and pushes the reconciled result. The target is resolved by `/check-merge` from the PR's base ref, so this works uniformly: - a **feature branch** syncs against its PR base (usually `main`), - a **branch with no PR** syncs against the repo default branch (`/check-merge`'s fallback) — the long-lived-branch case that keeps it a superset of the trunk. Its main entry is mid-work: the target moved while the branch is still being built and reviewed, and the operator wants it in before review goes on. `@.claude/skills/finalize/SKILL.md` runs it too, for its base merge. The skill merges **on the checked-out branch**, resolves conflicts mechanically and logically in a commit after the merge commit, verifies locally, and pushes proactively — the operator reviews the pushed resolution after the fact rather than through a pre-push gate. ## Argument shape ``` /sync-branch [<branch>] [no vet] ``` - **`<branch>`** (optional): a branch name, `#NNN` PR number, or PR URL — the same shape `/check-merge` and `/finalize` accept. Passing it makes …
Read the whole file at its exact version.
How to install
mdr add vzakharov/muthur/sync-branch@sha256:856a9c7dac5fceb9The line at the top of this page pins the label git:20261016.bb62c02, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_lyoko44ja2taf2rw)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Aug 8, 2026 and Oct 16, 2026, about one every 17 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261016.bb62c02 latest | 2026-10-16 | bb62c02 | 10,005 B | B | view · diff |
| git:20261015.b4741cf | 2026-10-15 | b4741cf | 9,852 B | B | view · diff |
| git:20261014.0f16275 | 2026-10-14 | 0f16275 | 7,359 B | B | view · diff |
| git:20260808.87faf05 | 2026-08-08 | 87faf05 | 7,353 B | B | view · diff |
| git:20260808.a6a6344 | 2026-08-08 | a6a6344 | 7,344 B | B | view |
Audit of the latest version
- fail: Frontmatter declares a name
- pass: Frontmatter block present
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (10005 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
vzakharov/muthur · 22 stars · license MIT · pushed 2026-10-30 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_lyoko44ja2taf2rw GET https://markdownregistry.com/api/v1/resolve?ref=vzakharov/muthur/sync-branch GET https://markdownregistry.com/api/v1/blob/856a9c7dac5fceb9576ca9d553f854aad5197a1bb39e41f6805e7463a07163d1
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from vzakharov/muthur
Every file in vzakharov/muthur